| 3 | Approval of the Agenda | |
|---|---|---|
| R3-233701 | RAN3#121 Meeting Agenda | RAN3 Chair |
| 4 | Approval of the minutes from previous meetings | |
| R3-233702 | RAN3#120 Meeting Report | ETSI-MCC |
| 5 | Documents for immediate consideration | |
| R3-233703 | Guidelines for RAN3 Meetings | RAN3 Chair, RAN3 Vice-Chairs |
| 7 | General, protocol principles and issues | |
| R3-234022 | TR 30.531 v1.47.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| R3-234494 | TR 30.531 v1.47.0 Work Plan and Working Procedures - RAN WG3 | ETSI-MCC |
| 8.1 | New Incoming LSs | |
| R3-233704 | Reply LS on Network Triggered Service Request for a UE in Suspend State | CT4(Ericsson) |
| R3-233707 | Reply LS on 1-symbol PRS | RAN1(ZTE) |
| R3-233710 | LS on Rel-18 higher-layers parameter list | RAN1(Ericsson) |
| R3-233724 | Reply LS on 3GPP work on Energy Efficiency | SA1(Nokia) |
| R3-233727 | Reply LS on the use of PEI during an emergency PDU session | SA2(Ericsson) |
| R3-233728 | Reply to LS on addressing packet loss during multicast MBS delivery | SA2(Ericsson) |
| R3-233736 | Reply LS on SCTP-AUTH and DTLS | SA3(Ericsson) |
| R3-233737 | LS on 3GPP work on Energy Efficiency | SA4(Qualcomm) |
| R3-233738 | Reply LS on introduction of a new attribute “Only Resource Coordination” to support source coordination between LTE and NR SA | SA5(China telecom) |
| R3-233812 | LS on information on actions taken by SG15 on inclusive language | RAN(Huawei) |
| R3-233836 | DTLS for SCTP next steps and request for input | IETF_TSVWG |
| R3-233843 | Conclusion on the use of PEI during emergency PDU session | Nokia, Nokia Shanghai Bell |
| R3-233844 | Response LS on the use of PEI during an emergency PDU session | Nokia, Nokia Shanghai Bell |
| R3-233845 | Correction of Paging with PEI | Nokia, Nokia Shanghai Bell |
| R3-233996 | Reply LS on introduction of a new attribute "Only Resource Coordination" to support source coordination between LTE and NR SA | China Telecom,Huawei |
| R3-233997 | Discussion on the attribute "isENDCAllowed" | China Telecom,Huawei,ZTE |
| R3-234194 | DTLS for SCTP: Summary and Further Discussion | Ericsson LM |
| R3-234195 | [DRAFT] Reply LS on DTLS for SCTP next steps and request for input | Ericsson LM |
| R3-234287 | Discussion on the on introduction of a new attribute “Only Resource Coordination” | Ericsson |
| R3-234373 | Consideration on packet loss during multicast MBS delivery | Huawei |
| R3-234374 | [DRAFT] Reply to LS on addressing packet loss during multicast MBS delivery | Huawei |
| R3-234375 | Clarification on gNB moving UEs to RRC_Inactive for active multicast session | Huawei |
| R3-234410 | Consideration on on introduction new attribute to support source coordination between LTE and NR SA | ZTE |
| R3-234411 | [Draft]Response LS on introduction new attribute to support source coordination between LTE and NR SA | ZTE |
| R3-234412 | Consideration on DTLS for SCTP | ZTE |
| R3-234413 | [Draft]Reply LS on DTLS for SCTP next steps and request for input | ZTE |
| R3-234469 | Discussion on DTLS for SCTP next steps - message size | Huawei |
| R3-234470 | [Draft] Reply LS on DTLS for SCTP next steps and request for input | Huawei |
| R3-234491 | Response to R3-233843 | Huawei |
| R3-234492 | Reply LS on DTLS for SCTP | SA3(Ericsson) |
| R3-234493 | LS on the user consent for trace reporting | SA3(Ericsson) |
| R3-234495 | CB: # 1_NewAttribute | ZTE |
| R3-234497 | Reply LS on DTLS for SCTP next steps and request for input | RAN3(Ericsson) |
| R3-234611 | [DRAFT] Reply to LS on addressing packet loss during multicast MBS delivery | Huawei |
| 8.2 | LSin received during the meeting | |
| R3-234532 | Support of Time Sensitive Networking (TSN) enabled Transport Network (TN) | CT4(Nokia) |
| R3-234560 | Reply LS on applicability of pre-configured measurement gaps for RedCap UE | RAN2(Qualcomm) |
| 9.1 | LTE | |
| R3-233917 | MDT user consent update in LTE and EN-DC | Huawei, Deutsche Telekom, Nokia, Nokia shanghai Bell, Ericsson |
| R3-233918 | MDT user consent update in EN-DC | Huawei, Deutsche Telekom, Nokia, Nokia shanghai Bell, Ericsson |
| R3-234471 | Further discussion on the presence of QoE area scope | ZTE, China Telecom, China Unicom, Ericsson |
| R3-234472 | Correction on QoE area scope tabular reference and presence | ZTE, Huawei, China Telecom, China Unicom, Ericsson |
| R3-234473 | Correction on QoE area scope tabular reference and presence | ZTE, Huawei, China Telecom, China Unicom, Ericsson |
| R3-234474 | Correction on QoE area scope tabular reference and presence | ZTE, Huawei, China Telecom, China Unicom, Ericsson |
| R3-234475 | Correction on presence of the QoE Area Scope IE | ZTE, China Telecom, China Unicom, Ericsson |
| R3-234476 | Correction on presence of the QoE Area Scope IE | ZTE, China Telecom, China Unicom, Ericsson |
| R3-234477 | Correction on presence of the QoE Area Scope IE | ZTE, China Telecom, China Unicom, Ericsson |
| R3-234498 | CB: # 3_MDTUserConsent | Huawei |
| R3-234502 | CB: # 4_QoEAreaScope | ZTE |
| R3-234644 | Correction on QoE area scope tabular reference and presence | ZTE, Huawei, China Telecom, China Unicom, Ericsson |
| R3-234645 | Correction on QoE area scope tabular reference and presence | ZTE, Huawei, China Telecom, China Unicom, Ericsson, Nokia, Noki |
| R3-234646 | Correction on QoE area scope tabular reference and presence | ZTE, Huawei, China Telecom, China Unicom, Ericsson |
| R3-234712 | Correction on QoE area scope tabular reference and presence | ZTE, Huawei, China Telecom, China Unicom, Ericsson, CATT, Nokia, Nokia Shanghai Bell |
| R3-234713 | Correction on QoE area scope tabular reference and presence | ZTE, Huawei, China Telecom, China Unicom, Ericsson,CATT, Nokia, Nokia Shanghai Bell |
| R3-234714 | Correction on QoE area scope tabular reference and presence | ZTE, Huawei, China Telecom, China Unicom, Ericsson, CATT, Nokia, Nokia Shanghai Bell |
| 9.2 | NR | |
| R3-233705 | Reply LS on the maximum length of Routing ID | CT4(Huawei) |
| R3-233817 | Clarification on R17 MO SDT termination | ZTE, China Telecom, Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo, CATT, Ericsson, Xiaomi |
| R3-233825 | Clarification on maximum length of Routing ID | NTT DOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-233826 | Clarification on maximum length of Routing ID | NTT DOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-233829 | UDC Parameters over E1 | Nokia, Nokia Shanghai Bell, China Telecom, ZTE, CATT, Huawei, Ericsson |
| R3-233833 | Correction to provide the slice availability for SN change procedure | Nokia, Nokia Shanghai Bell |
| R3-233839 | Inactive Time Signaling over E1 for Mobility | Nokia, Nokia Shanghai Bell |
| R3-233846 | Correction of MBS Distribution procedure | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Huawei, CATT, ZTE |
| R3-233847 | Correction of Distribution procedure | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Huawei, CATT, ZTE |
| R3-233848 | Correction of Location Dependent Service | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Huawei, CATT, ZTE |
| R3-233849 | Correction of Location Dependent Service | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Huawei, CATT, ZTE |
| R3-233850 | Correction of F1 Context Reference | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Huawei |
| R3-233851 | Correction of F1 Context Reference | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Huawei |
| R3-233864 | Partial QoS Flow release | NEC |
| R3-233865 | Correction for partial QoS release | NEC |
| R3-233866 | Correction for change of gNB-CU-UP | NEC |
| R3-233867 | Correction for change of gNB-CU-UP | NEC |
| R3-233868 | Correction for change of gNB-CU-UP | NEC |
| R3-233884 | Corrections to TS 38.401 for SL relay | ZTE Corporation, CAICT, China Telecom, Philips, CATT |
| R3-233894 | Clarification of the RAN UE ID usage in stage-2 | Ericsson, Orange, Deutsche Telekom, AT&T |
| R3-233895 | Downlink SRB1 forwarding for remote UE’s RRC Reestablishment/Resume procedure | Huawei, Interdigital, Nokia, Nokia Shanghai Bell, LG Electronics, NEC, ZTE, CATT, CMCC, China Telecom, Samsung |
| R3-233896 | Mapping of SRB1 for the remote UE | Huawei, Interdigital, Nokia, Nokia Shanghai Bell, LG Electronics, NEC, ZTE, CATT, CMCC, China Telecom, Samsung |
| R3-233897 | Correction of Mobility Information | Huawei, Ericsson, Qualcomm, BT, Deutsche Telekom, Vodafone |
| R3-233898 | Correction of Mobility Information | Huawei, Ericsson, Qualcomm, BT, Deutsche Telekom, Vodafone |
| R3-233915 | Correction on E-UTRA - NR Cell Resource Coordination | Huawei, Orange, China Telecom, Deutsche Telekom, Nokia, Nokia shanghai Bell, ZTE, Ericsson |
| R3-233916 | Correction on E-UTRA - NR Cell Resource Coordination | Huawei, Orange, China Telecom, Deutsche Telekom, Nokia, Nokia shanghai Bell, ZTE, Ericsson |
| R3-233919 | Correction on the local NG-RAN Node Identifier on Xn | Huawei, Nokia, Nokia shanghai Bell, ZTE |
| R3-233920 | Adding stage 2 text for MLB | Huawei, CMCC, China Telecom |
| R3-233921 | Adding stage 2 text for MLB | Huawei, CMCC, China Telecom |
| R3-233955 | Discussion on Avioding unnecessary setup of DRB(s) in indirect data forwarding | Samsung |
| R3-233956 | Avoiding unnecessary setup of DRB(s) in indirect data forwarding | Samsung |
| R3-233957 | Correction of QoS Flow Mapping Indication IE in PDU Session Resource Modification Required Info - SN terminated | Huawei, Deutsche Telekom, CATT, CMCC, Vodafone |
| R3-233958 | Correction of QoS Flow Mapping Indication IE in PDU Session Resource Modification Required Info - SN terminated | Huawei, Deutsche Telekom, CATT, CMCC, Vodafone |
| R3-233959 | Correction of QoS Flow Mapping Indication IE in PDU Session Resource Modification Required Info - SN terminated | Huawei, Deutsche Telekom, CATT, CMCC, Vodafone |
| R3-233960 | Correction of Additional PDCP Duplication TNL List | Huawei, Deutsche Telekom, Ericsson |
| R3-233961 | Correction of Additional PDCP Duplication TNL List | Huawei, Deutsche Telekom, Ericsson |
| R3-233971 | Transferring of IAB authorized info during inter-CU topology adaptation and backhaul RLF recovery procedure | ZTE, Lenovo, Xiaomi |
| R3-233972 | Transferring of IAB authorized info during inter-CU topology adaptation and backhaul RLF recovery procedure | ZTE, Lenovo, Xiaomi, CATT |
| R3-233973 | Transferring of IAB authorized info during inter-CU topology adaptation and backhaul RLF recovery procedure | ZTE, Lenovo, Xiaomi, CATT |
| R3-234042 | QoE Reference in QOE INFORMATION TRANSFER message | Ericsson |
| R3-234051 | Discussion on inter-node message for CU-DU split scenario | Samsung |
| R3-234052 | Correction to TS 38.473 on inter-node message for CU-DU split scenario | Samsung, ZTE, CATT, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-234053 | Correction to TS 38.473 on inter-node message for CU-DU split scenario | Samsung, ZTE, CATT, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-234054 | Correction on SI delivery to RedCap UE during handover | ZTE, China Telecom, CMCC |
| R3-234060 | Clarification on procedural description of Resource Status Reporting Initiation procedure over Xn | ZTE, China Telecom, China Unicom |
| R3-234061 | Clarification on procedural description of Resource Status Reporting Initiation procedure over Xn | ZTE, China Telecom, China Unicom |
| R3-234062 | Clarification on procedural description of Resource Status Reporting Initiation procedure over F1 | ZTE, China Telecom, China Unicom |
| R3-234063 | Clarification on procedural description of Resource Status Reporting Initiation procedure over F1 | ZTE, China Telecom, China Unicom |
| R3-234064 | Further clarification on maximum length of Routing ID | ZTE, China Telecom, China Unicom |
| R3-234065 | Correction on maximum length of Routing ID | ZTE, China Telecom, China Unicom |
| R3-234066 | Correction on maximum length of Routing ID | ZTE, China Telecom, China Unicom |
| R3-234067 | [DRAFT] Response to Reply LS on the maximum length of Routing ID | ZTE |
| R3-234077 | Correction of data forwarding for split PDU session | Huawei, Nokia, Noia Shanghai Bell, Qualcomm Incorporated, CMCC |
| R3-234078 | Correction of data forwarding for split PDU session | Huawei, Nokia, Noia Shanghai Bell, Qualcomm Incorporated, CMCC |
| R3-234079 | Correction of data forwarding for split PDU session | Huawei, Nokia, Noia Shanghai Bell, Qualcomm Incorporated, CMCC |
| R3-234080 | Correction on the sharedNGU-MulticastTNLInformation | Huawei, CBN, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, CATT, Ericsson, Orange, ZTE, BT |
| R3-234081 | Correction on MBS Session Forwarding Address | Huawei, CBN, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, CATT, Ericsson, Orange, ZTE, BT |
| R3-234082 | Correction on Fast MCG Recovery via SRB3 | Huawei, Deutsche Telekom, BT |
| R3-234083 | Correction on Fast MCG Recovery via SRB3 | Huawei, Deutsche Telekom, BT |
| R3-234092 | Discussion on misalignment of TAI between ASN.1 and tabular in QoE | Huawei, ZTE, InterDigital, China Unicom, Ericsson |
| R3-234093 | Correction to misalignment of TAI between ASN.1 and tabular in QoE | Huawei, ZTE, InterDigital, China Unicom, Ericsson |
| R3-234122 | Correction on SL relay F1AP ASN.1 IE semantics description | Philips International B.V. |
| R3-234123 | Correction on F1AP message name | Philips International B.V. |
| R3-234126 | Correction on F1AP message name | Philips International B.V. |
| R3-234136 | Correction on F1AP message name | Philips International B.V. |
| R3-234148 | Discussion on the BH info configuration for DRBs support CA based duplication | Huawei, Nokia, Nokia Shanghai Bell, CATT, Lenovo, Samsung |
| R3-234149 | Configuration of BH information for DRBs support CA based duplication | Huawei, Nokia, Nokia Shanghai Bell, CATT, Lenovo, Samsung |
| R3-234150 | Configuration of BH information for DRBs support CA based duplication | Huawei, Nokia, Nokia Shanghai Bell, CATT, Lenovo, Samsung |
| R3-234151 | Correction on IAB bar configuration | Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Xiaomi, CATT, Ericsson, Qualcomm, Samsung, ZTE |
| R3-234152 | Correction on IAB bar configuration | Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Xiaomi, CATT, Ericsson, Qualcomm, Samsung, ZTE |
| R3-234156 | Correction on mobility restriction list for MR-DC with 5GC | Huawei, Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-234157 | Correction on mobility restriction list for MR-DC with 5GC | Huawei, Nokia, Nokia Shanghai Bell, Deutsche Telekom |
| R3-234198 | Correction of Served Cell Specific Info Request | Huawei, Deutsche Telekom, BT |
| R3-234209 | Correction of presence of MBS CU to DU RRC Information IE in the BROADCAST CONTEXT MODIFICATION REQUEST message | ZTE, Ericsson, CATT, Lenovo, CMCC |
| R3-234210 | Correction on condition of successful MBS Broadcast Context Setup | ZTE, Huawei, CATT |
| R3-234214 | PRS CONFIGURATION REQUEST Correction | Huawei, Nokia, Nokia Shanghai Bell, CMCC?, Ericsson?, |
| R3-234215 | Positioning Information Transfer | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, CMCC |
| R3-234216 | Correction to missing NRPPa procedures | Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, CMCC |
| R3-234222 | Altitude correction for the NTN TRP | Huawei, Thales, Ericsson |
| R3-234223 | NTN Access Point Position | Huawei, Thales, Ericsson |
| R3-234224 | NTN Access Point Position | Huawei, Thales, Ericsson |
| R3-234225 | LS on Altitude for the Access Point | Huawei, Thales, Ericsson |
| R3-234226 | Correction concerning procedural text for "Unsuccessful Operation" specified in “Successful Operation” sections | Ericsson, AT&T, China Unicom, Deutsche Telekom, Interdigital |
| R3-234227 | Correction concerning procedural text for "Unsuccessful Operation" specified in “Successful Operation” sections | Ericsson, AT&T, China Unicom, Deutsche Telekom, Interdigital |
| R3-234228 | Correction concerning procedural text for "Unsuccessful Operation" specified in “Successful Operation” sections | Ericsson, AT&T, China Unicom, Deutsche Telekom, Interdigital |
| R3-234230 | Missing stage 2 specification for applicability of shared NG-U termination for Broadcast MBS Sessions | Ericsson, AT&T, CATT, China Unicom, Nokia, Nokia Shanghai Bell, ZTE |
| R3-234231 | Correction of control of mtch-neighbourCell content | Ericsson, AT&T, CATT, China Unicom, ZTE |
| R3-234240 | Clarification on the presence of Broadcast PLMN Identity Info List NR IE | CATT, ZTE |
| R3-234241 | Clarification on the presence of Broadcast PLMN Identity Info List NR IE | CATT, ZTE |
| R3-234242 | ASN.1 and tabular alignment for Broadcast related messages | CATT, Nokia, Nokia Shanghai Bell, Ericsson, ZTE,China Telecom, CBN |
| R3-234243 | Data forwarding handling of MRB in split target gNB | CATT,China Telecom,CBN |
| R3-234244 | Correction to F1AP on Data forwarding handling of MRB | CATT, China Telecom, CBN |
| R3-234245 | Correction to E1AP on Data forwarding handling of MRB | CATT, ZTE, Ericsson, China Telecom, CBN |
| R3-234260 | Correction of Positioning SIType List | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, ZTE, CATT |
| R3-234261 | Correction of Positioning SIType List | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, ZTE, CATT |
| R3-234262 | Correction on Positioning SI handling over F1 | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, ZTE, CATT |
| R3-234263 | Correction on Positioning SI handling over F1 | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, ZTE, CATT |
| R3-234324 | Solving Misalignment in UE Context Release procedure | Ericsson |
| R3-234325 | Solving Misalignment in UE Context Release procedure | Ericsson |
| R3-234330 | Restriction of NIA0 algorithm in gNB-CU-UP | Ericsson |
| R3-234331 | Restriction of NIA0 algorithm in gNB-CU-UP | Ericsson |
| R3-234332 | Restriction of NIA0 algorithm in gNB-CU-UP | Ericsson |
| R3-234334 | Correction of I-RNTI | Nokia, Nokia Shanghai Bell |
| R3-234335 | Correction of MBS Neighbour cells | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, CATT, Ericsson |
| R3-234336 | Correction of MBS Neighbour cells | Nokia, Nokia Shanghai Bell, Orange, Ericsson, Qualcomm Incorporated, CATT |
| R3-234353 | Correction on wrong abnormal description for conditional mobility in F1AP UE Context Modification procedure | LG Electronics Inc. |
| R3-234354 | Rel-16 Correction in the UE Context Modification procedure abnormal description for conditional mobility modification | LG Electronics Inc. |
| R3-234355 | Rel-17 Correction in the UE Context Modification procedure abnormal description for conditional mobility modification | LG Electronics Inc. |
| R3-234356 | Clarify the encoding of UE Radio Capability over NGAP | CATT |
| R3-234357 | Clarify the encoding of UE Radio Capability over NGAP | CATT |
| R3-234405 | Correction on non-SDT or oversize SDT data arrvial during on-going SDT session | China Telecom |
| R3-234445 | Discussion on exchanging AMF Set information over Xn | CMCC, Huawei, ZTE, CATT |
| R3-234456 | Misalignment between tabular and ASN.1 for CHO Information IE | Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, China Telecom |
| R3-234457 | Misalignment between tabular and ASN.1 for CHO Information IE | Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, China Telecom |
| R3-234463 | Correction on misalignment between tabular and ASN.1 for positioning_Option1 | ZTE, Xiaomi, CATT |
| R3-234464 | Correction on misalignment between tabular and ASN.1 for positioning_Option1 | ZTE, Xiaomi, CATT |
| R3-234465 | Correction on misalignment between tabular and ASN.1 for positioning_Option2 | ZTE, Xiaomi, CATT |
| R3-234466 | Correction on misalignment between tabular and ASN.1 for positioning_Option2 | ZTE, Xiaomi, CATT |
| R3-234490 | Editorial correction for IE PRS Configuration in PRS Configuration Response | RadiSys |
| R3-234499 | Solving Misalignment in UE Context Release procedure | Ericsson |
| R3-234500 | Solving Misalignment in UE Context Release procedure | Ericsson |
| R3-234503 | Clarification on maximum length of Routing ID | NTT DOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE |
| R3-234504 | Clarification on maximum length of Routing ID | NTT DOCOMO, INC., Nokia, Nokia Shanghai Bell, Ericsson, Huawei, ZTE |
| R3-234509 | Misalignment between tabular and ASN.1 for CHO Information IE | Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, China Telecom |
| R3-234510 | Misalignment between tabular and ASN.1 for CHO Information IE | Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, China Telecom |
| R3-234511 | PRS CONFIGURATION REQUEST Correction | Huawei, Nokia, Nokia Shanghai Bell, CMCC, Ericsson |
| R3-234512 | Correction of Mobility Information | Huawei, Ericsson, Qualcomm, BT, Deutsche Telekom, Vodafone, Nokia, Nokia Shanghai Bell |
| R3-234513 | Correction of Mobility Information | Huawei, Ericsson, Qualcomm, BT, Deutsche Telekom, Vodafone, Nokia, Nokia Shanghai Bell |
| R3-234514 | Clarification on R17 MO SDT termination | ZTE, China Telecom, Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Lenovo, CATT, Ericsson, Xiaomi, LG Electronics, Samsung |
| R3-234515 | Correction of MBS Distribution procedure | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Huawei, CATT, ZTE |
| R3-234516 | Correction of Distribution procedure | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Huawei, CATT, ZTE |
| R3-234517 | CB:#5_MBSNeighbourcell | Nokia |
| R3-234518 | Correction on condition of successful MBS Broadcast Context Setup | ZTE, Huawei, CATT, Nokia, Nokia Shanghai Bell |
| R3-234519 | CB:#6_MRBinSplitCase | CATT |
| R3-234520 | Correction of Location Dependent Service | Nokia, Nokia Shanghai Bell, Orange, Qualcomm Incorporated, Huawei, CATT, ZTE |
| R3-234521 | Mapping of SRB1 for the remote UE | Huawei, Interdigital, Nokia, Nokia Shanghai Bell, LG Electronics, NEC, ZTE, CATT, CMCC, China Telecom, Samsung, Ericsson |
| R3-234522 | Corrections to TS 38.401 for SL relay | ZTE Corporation, CAICT, China Telecom, Philips, CATT, Ericsson |
| R3-234523 | Correction on E-UTRA - NR Cell Resource Coordination | Huawei, Orange, China Telecom, Deutsche Telekom, Nokia, Nokia shanghai Bell, ZTE, Ericsson |
| R3-234524 | Correction on the local NG-RAN Node Identifier on Xn | Huawei, Nokia, Nokia shanghai Bell, ZTE, Ericsson |
| R3-234525 | Correction on IAB bar configuration | Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Xiaomi, CATT, Ericsson, Qualcomm, Samsung, ZTE |
| R3-234526 | Correction on IAB bar configuration | Huawei, Nokia, Nokia Shanghai Bell, Lenovo, Xiaomi, CATT, Ericsson, Qualcomm, Samsung, ZTE |
| R3-234527 | CB:#7_TNLAddress | Huawei |
| R3-234528 | Correction of data forwarding for split PDU session | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, CMCC, Orange, ZTE, Ericsson |
| R3-234529 | Correction of data forwarding for split PDU session | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, CMCC, Orange, ZTE, Ericsson |
| R3-234530 | Correction on mobility restriction list for MR-DC with 5GC | Huawei, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Orange |
| R3-234531 | CB:#8_InactiveTimeOver E1 | Nokia |
| R3-234554 | Correction on non-SDT or oversize SDT data arrvial during on-going SDT session | China Telecom, ZTE, Huawei, CATT |
| R3-234608 | Correction of Additional PDCP Duplication TNL List | Huawei, Deutsche Telekom, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-234609 | Correction of Additional PDCP Duplication TNL List | Huawei, Deutsche Telekom, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-234610 | Correction on mobility restriction list for MR-DC with 5GC | Huawei, Nokia, Nokia Shanghai Bell, Deutsche Telekom, Orange |
| R3-234618 | Rel-17 Correction in the UE Context Modification procedure abnormal description for conditional mobility modification | LG Electronics Inc. |
| R3-234619 | Correction on non-SDT arrvial during on-going SDT session | China Telecom, ZTE, Huawei, CATT |
| R3-234681 | Correction on the local NG-RAN Node Identifier on Xn [RRCInactive] | Huawei, Nokia, Nokia shanghai Bell, ZTE, Ericsson |
| R3-234682 | Correction of data forwarding for split PDU session | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, CMCC, Orange, ZTE, Ericsson, CATT |
| R3-234683 | Correction of data forwarding for split PDU session | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, CMCC, Orange, ZTE, Ericsson, CATT |
| R3-234684 | Misalignment between tabular and ASN.1 for CHO Information IE | Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, China Telecom |
| R3-234686 | Correction on non-SDT data arrival during on-going SDT session | China Telecom, ZTE, Huawei, CATT, Samsung, Nokia, Nokia shanghai Bell, Ericsson |
| R3-234687 | Clarify the encoding of UE Radio Capability over NGAP | CATT |
| R3-234688 | Clarify the encoding of UE Radio Capability over NGAP | CATT |
| R3-234696 | Correction on the local NG-RAN Node Identifier on Xn [RRCInactive] | Huawei, Nokia, Nokia shanghai Bell, ZTE, Ericsson, Orange |
| R3-234722 | Inactive Time Signaling over E1 for Mobility | Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R3-234732 | Inactive Time Signaling over E1 for Mobility | Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R3-234733 | Inactive Time Signaling over E1 for Mobility | Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R3-234739 | Inactive Time Signaling over E1 for Mobility | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei, CATT |
| R3-234740 | Inactive Time Signaling over E1 for Mobility | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei, CATT |
| R3-234741 | Inactive Time Signaling over E1 for Mobility | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei, CATT |
| R3-234775 | Transferring of IAB authorized info during inter-CU topology adaptation and backhaul RLF recovery procedure | ZTE, Lenovo, Xiaomi, CATT |
| 9.3 | R17 Rapporteur Corrections | |
| R3-234076 | LPPa Rapporteur Update | Ericsson LM |
| R3-234232 | Further Rapporteur's Corrections | Ericsson |
| R3-234264 | NRPPa Rapporteur Corrections | Rapporteur (Ericsson) |
| R3-234333 | Rapporteur's correction of misplaced procedural text | Ericsson |
| R3-234458 | X2AP rapporteur corrections | Ericsson |
| 10.1 | General | |
| R3-233740 | (BL CR to 36.423) Addition of SON features enhancement | CATT |
| R3-233748 | (BLCR to 38.413) for MDT | Ericsson |
| R3-233757 | (BLCR to 38.423) for MDT | Huawei |
| R3-233758 | (BLCR to 38.423) Addition of SON features enhancement | Samsung |
| R3-233772 | (BLCR to 36.300) Addition of SON features enhancement | Lenovo |
| R3-233775 | (BLCR to 37.340) Addition of SON Rel.18 features | Nokia, Nokia Shanghai Bell |
| R3-233781 | (BLCR to 38.300) Addition of SON features enhancement | CMCC |
| R3-233790 | (BLCR to 38.401) Addition of SON features enhancement | ZTE |
| R3-233794 | (BLCR to 38.413) for SON | Ericsson |
| R3-233802 | (BLCR to 38.470) Addition of SON features enhancement | CMCC |
| R3-233805 | (BLCR to 38.473) Addition of SON features enhancement | Huawei |
| R3-234372 | (BL CR to 36.423) Addition of SON features enhancement | CATT |
| R3-234431 | Update of work Plan for Enhancement of Data Collection for SON_MDT in NR standalone and MR-DC WI | CMCC |
| R3-234538 | (BLCR to 38.470) Addition of SON features enhancement | CMCC |
| R3-234787 | (BL CR to 36.300) Addition of SON features enhancement | Lenovo |
| R3-234788 | (BL CR to 36.423) Addition of SON features enhancement | CATT |
| R3-234789 | (BL CR to 37.340) Addition of SON Rel.18 features | Nokia, Nokia Shanghai Bell |
| R3-234790 | (BL CR to 38.300) Addition of SON features enhancement | CMCC |
| R3-234791 | (BLCR to 38.413) for SON | Ericsson |
| R3-234792 | (BLCR to 38.423) for MDT | Huawei |
| R3-234793 | (BLCR to 38.423) Addition of SON features enhancement | Samsung |
| R3-234794 | (BL CR to 38.473) Addition of SON features enhancement | Huawei |
| R3-234845 | (BLCR to 38.413) for MDT | Ericsson España S.A. |
| 10.2.1 | SHR and SPR | |
| R3-233718 | Reply LS on SHR and SPR | RAN2(Huawei) |
| R3-233877 | Discussion on remaining issue of inter-RAT SHR | NEC |
| R3-233899 | SHR and SPR | Huawei |
| R3-233922 | Successful Handover Report and Successful PSCell Change Report | Qualcomm Incorporated |
| R3-233931 | (TP for SON BLCR for 38.423 and 38.300) SON enhancement for SHR | Samsung |
| R3-233932 | (TP for SON BLCR for 37.340) SON enhancement for SPR | Samsung |
| R3-234108 | (TP for SON 37.340 and 38.300) Discussion on SON enhancement for SHR and SPR | CATT |
| R3-234172 | SON enhancements for SHR and SPR | Lenovo |
| R3-234310 | (TP for SON BL CR for TS 38.423) Successful PSCell Report (SPR) for SON rel-18 | Ericsson |
| R3-234316 | (TPs for SON BLCR for TS 38.423)Inter-RAT SHR and SPR | Nokia, Nokia Shanghai Bell |
| R3-234414 | (TPs for SON BLCRs for TS 38.423)Inter-RAT SHR and SPR | ZTE |
| R3-234432 | Discussion on SON enhancement for Inter-RAT SHR | CMCC, Nokia, Nokia Shanghai Bell |
| R3-234433 | Discussion on SON enhancement for SPR | CMCC |
| R3-234539 | CB:SONMDT1_SHRSPR | Qualcomm |
| R3-234612 | [DRAFT] Reply LS on SHR and SPR | RAN3(Huawei) |
| R3-234716 | Reply LS on SHR and SPR | RAN3(Huawei) |
| 10.2.2 | MRO | |
| R3-233878 | Discussion on remaining issue of MRO | NEC |
| R3-233900 | (TPs for SON BLCRs for TS 38.423) MRO on CPAC | Huawei |
| R3-233901 | (TPs for SON BLCRs for TS 38.413) MRO on fast MCG recovery and voice fallback | Huawei |
| R3-233923 | MRO enhancements for CPAC, voice fallback and fast MCG recovery | Qualcomm Incorporated |
| R3-233933 | (TP for SON BLCR for 38.423 and 37.340) SON enhancements for CPAC and MCG failure recovery | Samsung |
| R3-233934 | (TP for SON BLCR for 38.413) MRO for inter-system handover for voice fallback | Samsung |
| R3-234055 | (TP for SON BL CR TS38.413) MRO enhancements in Rel-18 | ZTE |
| R3-234109 | (TP for SON for 37.340 and 38.423) Discussion on MRO enhancement for CPAC | CATT |
| R3-234110 | (TP for SON 38.413) Discussion on MRO enhancement for fast MCG recovery and voice fallback | CATT |
| R3-234173 | MRO for CPAC | Lenovo |
| R3-234174 | MRO for fast MCG recovery and voice fallback | Lenovo |
| R3-234175 | Update of the MRO scenarios | Lenovo, Qualcomm Incorporated, Huawei |
| R3-234311 | (TP for SON BL CR for TS 37.340) SON enhancements for MRO | Ericsson |
| R3-234323 | (TPs for SON BLCR for TS 38.423) Further discussion on the MRO for CPAC and for the fast MCG recovery | Nokia, Nokia Shanghai Bell |
| R3-234434 | Discussion on MRO for CPAC | CMCC |
| R3-234540 | CB:#SONMDT2_MRO | Samsung |
| R3-234625 | (TP for SON BL CR 38.413) Introduction of a new handover report type for inter-system voice fallback | CATT |
| R3-234665 | (TP for SON BLCR for 38.423) SON enhancements for CPAC | Samsung, Cybercore |
| R3-234666 | (TP for SON BLCR for 37.340) UHI for CPAC | Samsung, Ericsson, Nokia, Nokia Shanghai Bell |
| 10.2.3 | RACH Enhancements | |
| R3-233715 | Reply LS on RACH enhancement | RAN2(ZTE) |
| R3-233924 | RACH optimization enhancements | Qualcomm Incorporated |
| R3-233935 | Discussion on SON for RACH | Samsung |
| R3-234068 | (TPs for SON BLCR for TS 36.300, TS38.300 and TS 38.473): Remaining issues for RACH optimisation | Huawei |
| R3-234069 | (TP for SON BLCR for TS 38.420): Introduction of RACH Indication | Huawei, China Telecom, CMCC |
| R3-234111 | Discussion on RACH enhancement | CATT |
| R3-234131 | Discussion on RACH optimization | Nokia, Nokia Shanghai Bell |
| R3-234176 | Discussion on SN RACH enhancements | Lenovo |
| R3-234312 | RACH Optimization enhancement | Ericsson |
| R3-234415 | (TPs for SON BLCRs for TS36.423 TS 38.423 TS 38.473 TS 37.340)RACH enhancements | ZTE |
| R3-234416 | [Draft]Reply LS on Reply LS on RACH enhancement | ZTE |
| R3-234541 | CB:SONMDT3_RACH | Huawei |
| R3-234643 | LS on RACH enhancement | RAN3(Huawei) |
| R3-234647 | (TP for SON BLCR fo TS 36.423): Remaining issues for RACH optimisation | Huawei |
| R3-234648 | (TP for SON BLCR for TS 38.420): Introduction of RACH Indication | Huawei, China Telecom, CMCC |
| R3-234649 | (TP for SON BLCR for TS 36.300): Remaining issues for RACH optimisation | Huawei |
| R3-234650 | (TP for SON BLCR for TS 38.300): Remaining issues for RACH optimisation | Huawei |
| R3-234671 | (TPs for SON BLCRs for TS 38.423 )RACH enhancements | ZTE |
| R3-234672 | (TPs for SON BLCRs for TS 38.473 )RACH enhancements | ZTE |
| R3-234695 | (TP for SON BLCR for TS 37.340): Remaining issues for RACH optimisation | Huawei |
| R3-234742 | (TP for SON BLCR for TS 38.420): Introduction of RACH Indication | Huawei, China Telecom, CMCC, Ericsson, ZTE |
| R3-234743 | (TPs for SON BLCRs for TS 38.423): RACH enhancements | ZTE, Ericsson, Huawei, Nokia, Nokia Shanghai Bell |
| R3-234827 | (BL CR to 38.420) SON Introduction of RACH Indication | Huawei |
| 10.2.4 | SON/MDT Enhancements for Non-Public Networks | |
| R3-234070 | Remaining issues for MDT in NPN | Huawei, Deutsche Telekom, CMCC |
| R3-234071 | (TP for MDT BL CR for TS 38.413): Remaining issues for MDT in NPN | Huawei, Deutsche Telekom, CMCC |
| R3-234072 | (TP for MDT BLCR for TS 37.320): MDT support in NPN | Huawei, Orange, China Telecom, CMCC |
| R3-234132 | Introduction of MDT enhancements to support Non-Public Networks | Nokia, Nokia Shanghai Bell |
| R3-234197 | (TP for MDT BL CR for TS 38.423): Remaining issues for MDT in NPN | Huawei, Deutsche Telekom, CMCC |
| R3-234199 | MDT enhancement for NPN | CATT |
| R3-234313 | (TP for SON to BLCR for TS38.413, TS38.423, TS38.370) SON enhancements for Non-public networks | Ericsson |
| R3-234314 | Reply LS on user consent of Non-public Network | Ericsson |
| R3-234417 | (TPs for MDT BLCRs for TS38.413 TS 37.320)MDT support in NPN | ZTE |
| R3-234542 | CB:#SONMDT4_NPN | ZTE |
| R3-234607 | Introduction of MDT enhancements to support Non-Public Networks | Nokia, Nokia Shanghai Bell |
| R3-234641 | (TP for MDT BLCRs for TS38.423 )MDT support in NPN | Huawei |
| R3-234675 | (TPs for MDT BLCRs for TS38.413) MDT support in NPN | ZTE |
| R3-234717 | LS on SON for NPN | RAN3(Ericsson) |
| R3-234718 | (TP for MDT BLCRs for TS38.413 )MDT support in NPN | ZTE, Ericsson, Huawei, Nokia,Nokia Shanghai Bell |
| R3-234719 | (TP for MDT BLCRs for TS38.423 )MDT support in NPN | Huawei, Ericsson, ZTE |
| R3-234720 | Introduction of MDT enhancements to support Non-Public Networks | Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei |
| R3-234721 | Reply LS on user consent of Non-public Network | Ericsson |
| R3-234723 | LS on SON for NPN | RAN3(Ericsson) |
| R3-234744 | LS on SON for NPN | RAN3(Ericsson) |
| R3-234826 | (BL CR to 38.413) MDT support in NPN | Ericsson España S.A. |
| 10.2.5 | SON for NR-U | |
| R3-233862 | Further discussion on LBT waiting time for correct classification of MRO events and optimisation of the EDT | Nokia, Nokia Shanghai Bell |
| R3-233925 | SON enhancements for NR-U | Qualcomm Incorporated |
| R3-233936 | Discussion on SON for NR-U | Samsung |
| R3-234056 | Further discussion on NR-U optimizations | ZTE |
| R3-234073 | (TP for MDT BL CR for TS 38.300): SON for NR-U | Huawei |
| R3-234112 | (TP for SON for TS 38.473) Discussion on SON enhancement for NR-U | CATT |
| R3-234177 | (TP for SON BLCR to TS38.423) Discussion on MRO for NR-U | Lenovo |
| R3-234315 | (TP for SON BL CR for TS 38.423, TS 38.473) NR-U enhancements for MRO and MLB | Ericsson |
| R3-234543 | CB:'SONNMDT5_NRU | Ericsson |
| R3-234544 | (TP for SON BL CR for 38.423) NR-U enhancements for MLB | Ericsson, ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Huawei |
| R3-234545 | (TP for SON BL CR for 38.473) NR-U enhancements for MLB | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, Huawei |
| 10.2.6 | MDT Enhancements | |
| R3-234133 | Further discussion on signalling based logged MDT override protection | Nokia, Nokia Shanghai Bell |
| R3-234418 | (TPs for MDT BLCRs for TS 38.413)MDT Enhancements | ZTE |
| 11.1 | General | |
| R3-233762 | QoE in NR-DC | Ericsson |
| R3-233777 | (BLCR to 37.340) QMC enhancements for NR-DC | Nokia, Nokia Shanghai Bell, ZTE, China Unicom, Orange, Ericsson |
| R3-233785 | Support of Enhancement of NR QoE | China Unicom |
| R3-233792 | (BLCR) Enhancement on NR QoE | Samsung |
| R3-233795 | (BLCR to 38.413) Introduction of R18 QoE measurement | Huawei, China Telecom, China Unicom |
| R3-233807 | Enhancement on NR QoE | ZTE |
| R3-234385 | Update Workplan for Rel-18 NR QoE Enhancement | China Unicom |
| R3-234389 | Support of Enhancement of NR QoE | China Unicom |
| R3-234620 | (BLCR to 38.423) Introduction of R18 QoE measurement | Ericsson |
| R3-234621 | (BLCR to 38.401) Introduction of R18 QoE measurement | Samsung |
| R3-234622 | (BLCR to 38.473) Introduction of R18 QoE measurement | ZTE |
| R3-234623 | (BLCR to 38.300) Introduction of R18 QoE measurement | China Unicom |
| R3-234809 | (BL CR to 37.340) QMC enhancements for NR-DC | Nokia, Nokia Shanghai Bell, ZTE, China Unicom, Orange, Ericsson |
| R3-234810 | (BL CR to 38.300) Introduction of R18 QoE measurement | China Unicom |
| R3-234811 | (BL CR to 38.423) Introduction of R18 QoE measurement | Ericsson |
| 11.2 | Support for New Service Type and RRC_INACTIVE/RRC_IDLE states | |
| R3-233711 | LS on area scope for QoE measurements | RAN2(Samsung) |
| R3-233926 | QMC for applications carried over MBS broadcast and multicast | Qualcomm Incorporated |
| R3-233927 | QoE enhancements for high mobility scenarios | Qualcomm Incorporated |
| R3-234029 | Remaining issues on QMC for MBS and RRC state | Samsung |
| R3-234030 | [draft] Reply LS on area scope for QoE measurements | Samsung |
| R3-234043 | QoE and RVQoE Measurement Collection for Sessions Carried via MBS | Ericsson |
| R3-234044 | QMC in HSDN Cells and High Mobility Scenarios | Ericsson |
| R3-234094 | Further discussion on the support of MBS QoE | Huawei |
| R3-234095 | [draft] Reply LS to Reply LS on QoE measurements in RRC IDLE/INACTIVE states | Huawei |
| R3-234096 | [draft] Reply LS on area scope for QoE measurements | Huawei |
| R3-234127 | Continued discussion on solutions for QMC in RRC_IDLE | Nokia, Nokia Shanghai Bell |
| R3-234178 | Discussion on QoE measurement in RRC_INACTIVE and RRC_IDLE states | Lenovo |
| R3-234179 | (TP to 38.423 & 38.420) Support of QoE measurement in RRC_INACTIVE | Lenovo |
| R3-234248 | QoE configuration and reporting in RRC_INACTIVE RRC_IDLE states | Xiaomi |
| R3-234390 | Discussion on NR QoE in RRC_INACTIVE/RRC_IDLE states | CATT |
| R3-234401 | Discussion on QoE measurement in RRC_INACTIVE and RRC_IDLE states | China Unicom |
| R3-234478 | Discussion on INACTIVE/IDLE QoE and high mobility QoE | ZTE, China Telecom, CMCC |
| R3-234479 | Draft reply LS to RAN2 on area scope for QoE measurements | ZTE |
| R3-234624 | CB:#QoE1_Inactive | Lenovo |
| R3-234694 | LS on QMC support in RRC_IDLE and RRC_INACTIVE states | RAN3(Ericsson) |
| R3-234711 | Reply LS on area scope for QoE measurements | RAN3(Samsung) |
| R3-234745 | LS on QMC support in RRC_IDLE and RRC_INACTIVE | RAN3(Ericsson) |
| R3-234746 | Reply LS on area scope for QoE measurements | RAN3(Samsung) |
| 11.3 | Support QoE for NR-DC | |
| R3-233928 | Support for QoE in NR-DC | Qualcomm Incorporated |
| R3-234031 | Remaining issues on support of NR-DC | Samsung |
| R3-234045 | (TPs for QoE BL CR for TS 37.340 and TS 38.300) QoE and RVQoE Measurements and Reporting in NR-DC Scenarios | Ericsson |
| R3-234097 | Further discussion on the support for QoE in NR-DC | Huawei |
| R3-234098 | (TP for 38.423) on QoE measurement enhancements | Huawei |
| R3-234128 | Further discussion on QoE/RVQoE measurement report continuity and RAN overload in NR-DC | Nokia, Nokia Shanghai Bell |
| R3-234180 | Discussion on QoE measurement in NR-DC | Lenovo |
| R3-234249 | Discussion on QoE configuration and reporting in NR-DC | Xiaomi |
| R3-234391 | Discussion on Support for legacy QoE in NR-DC | CATT |
| R3-234392 | Discussion on Support for RV-QoE in NR-DC | CATT |
| R3-234402 | Discussion on QoE measurement in NR-DC | China Unicom |
| R3-234403 | (TP to BL CR of 38.423) QoE in NR-DC | China Unicom |
| R3-234421 | Discussion on QoE in NR-DC | ZTE, China Unicom, China Telcom |
| R3-234422 | (TP to BL CR of 38.423) QoE in NR-DC | ZTE, China Unicom, China Telecom |
| R3-234423 | (TP to BL CR of 37.340) QoE in NR-DC | ZTE, China Unicom |
| R3-234591 | (TP to BL CR of 38.423) QoE in NR-DC | ZTE, China Unicom, China Telecom |
| R3-234606 | Summary of offline on QoE in NR-DC | ZTE |
| R3-234617 | (TP to 37.340) QMC enhancements for NR-DC | Huawei |
| R3-234626 | CB:#QoE2_NRDC (*cancelled allocation) | nn |
| R3-234627 | (TP to BL CR of 38.423) QoE in NR-DC | ZTE, China Unicom, China Telecom |
| R3-234628 | (TP to 37.340) QMC enhancements for NR-DC | Huawei |
| R3-234629 | (TP for QoE BL CR TS 38.300) QoE and RVQoE Measurements and Reporting in NR-DC | Ericsson |
| R3-234630 | LS to RAN2 on RAN3 progress on QoE in NR-DC | RAN3(ZTE) |
| R3-234747 | (TP to 37.340) QMC enhancements for NR-DC | Huawei, ZTE, Ericsson, CATT |
| R3-234748 | (TP to BL CR of 38.423) QoE in NR-DC | ZTE, China Unicom, China Telecom, Ericsson, Huawei, CATT, Xiaomi, Nokia, Nokia Shanghai Bell, Samsung |
| R3-234749 | (TP for QoE BL CR TS 38.300) QoE and RVQoE Measurements and Reporting in NR-DC | Ericsson, ZTE |
| R3-234750 | LS on RAN3 progress on QoE in NR-DC | RAN3(ZTE) |
| 11.4 | Others | |
| R3-233813 | Reply LS on buffer level threshold-based RVQoE reporting | SA4(Apple) |
| R3-233929 | Threshold based reporting for buffer level | Qualcomm Incorporated |
| R3-234046 | (TP for QoE BL CR for TS 38.473) Enhancements of Rel-17 QoE and RVQoE Features | Ericsson |
| R3-234099 | Further discussion on the support of R17 left-over features and inter RAT handover | Huawei, China Unicom, China Telecom |
| R3-234129 | (TP for BLCR to TS 38.473) Discussion on report deactivation in F1 interface | Nokia, Nokia Shanghai Bell, ZTE, Xiaomi |
| R3-234130 | LS-related discussions | Nokia, Nokia Shanghai Bell |
| R3-234181 | Discussion on QoE measurement during intra-5GC inter-RAT handover | Lenovo |
| R3-234250 | Discussion on R17 leftovers | Xiaomi |
| R3-234393 | Discussion on Left-over issues | CATT |
| R3-234404 | NR QoE continuity during intra-5GC inter-RAT handover | China Unicom |
| R3-234424 | Discussion on other issues | ZTE, China Unicom, China Telecom, CMCC |
| R3-234425 | (TPs for BL CR of TS38.401&38.470) Deactivation of RVQoE reporting over F1AP | ZTE, Nokia, Nokia Shanghai Bell, China Unicom, China Telecom |
| R3-234559 | Consolidated proposals from QoE AI 11.4 | Ericsson |
| 12.1 | General | |
| R3-233756 | (BLCR to 38.423) for AI/ML for NG-RAN | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-233780 | Draft CR to 38.300 on AI/ML for NG-RAN | CMCC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, Samsung, Lenovo, Intel Corporation |
| R3-233789 | CR to TS 38.401 for addition of AI/ML-RAN feature in the case of split architecture | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Samsung, Intel Corporation, CMCC |
| R3-234444 | Work plan for Rel-18 AI/ML for NG-RAN | CMCC, Ericsson |
| R3-234785 | (BL CR to 38.300) AI/ML for NG-RAN | CMCC, ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, Samsung, Lenovo, Intel Corporation, China Unicom, InterDigital, Qualcomm Incorporated |
| R3-234786 | (BLCR to 38.423) for AI/ML for NG-RAN | Ericsson, Nokia, Nokia Shanghai Bell |
| 12.2.1 | Stage2 Related | |
| R3-233874 | AI/ML predicting accuracy | NEC |
| R3-233911 | Discussion on Prediction Time and Accuracy | Intel Corporation |
| R3-233937 | Discussion on time information in AI/ML information reporting | Samsung |
| R3-233995 | Discussion on Xn Enhancements for NG-RAN AI/ML | Qualcomm Incorporated |
| R3-234002 | Discussion on validity time and prediction accuracy | China Telecommunication |
| R3-234185 | (TP for TS38.423 BLCR) On the naming of the new procedures | Lenovo |
| R3-234186 | Discussion on the time information in the request message | Lenovo |
| R3-234187 | Discussion on prediction accuracy | Lenovo |
| R3-234203 | (TP to 38.423) Discussion on the duration for which the prediction is | CATT |
| R3-234278 | Further discussions on common issues and Stage 2 updates on the introduction of RAN AI/ML | Huawei |
| R3-234279 | (TP for AI/ML BL CR for TS 38.300) Stage 2 updates on the introduction of RAN AI/ML | Huawei, CATT, China Unicom |
| R3-234288 | Discussion on AI/ML Procedures Names | Ericsson, InterDigital, Nokia, Nokia Shanghai Bell, Deutsche Telekom, AT&T, CATT, Orange |
| R3-234289 | (TP for AI/ML BLCR to TS38.423) Procedure Name | Ericsson, InterDigital, Nokia, Nokia Shanghai Bell, Deutsche Telekom, AT&T, CATT, Orange |
| R3-234290 | (TP for AI/ML BLCR to TS38.300) Characteristics of the procedures for exchanging AI/ML-related information | Ericsson, InterDigital |
| R3-234291 | Open points on requested prediction time | Ericsson, InterDigital, Deutsche Telekom |
| R3-234292 | (TP for AI/ML on BLCR to TS38.423) Requested prediction time | Ericsson, InterDigital, Deutsche Telekom |
| R3-234328 | Characteristics of the procedures for exchanging AI/ML-related information | Ericsson, InterDigital |
| R3-234340 | (TP for TS 38.423) Timing Information and Confidence Discussion | Nokia, Nokia Shanghai Bell |
| R3-234376 | (TP to 38.423 & 38.300) Further discussion on Timing Information | ZTE |
| R3-234386 | Discussion on open issues related to predicted time information | LG Electronics Inc. |
| R3-234387 | (TP for NR_AIML_NGRAN-Core BL CR for TS 38.423) Discussion on open issues related to predicted time information | LG Electronics Inc. |
| R3-234441 | Discussion on AIML time information | CMCC |
| R3-234547 | CB:#AIRAN1_Timeinfor | ZTE |
| R3-234658 | (TP for AI/ML BL CR for TS 38.300) Stage 2 updates on the introduction of RAN AI/ML | Huawei, CATT, China Unicom |
| R3-234663 | (TP to 38.423) Requested prediction time | ZTE, Samsung, Lenovo, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, CATT, CMCC, Qualcomm Incorporated |
| R3-234724 | (TP for AI/ML BLCR to TS38.423) Procedure Name | Ericsson, InterDigital, Nokia, Nokia Shanghai Bell, Deutsche Telekom, AT&T, CATT, Orange |
| 12.2.2.1 | LB and Xn procedures | |
| R3-233875 | AI/ML Load Balancing | NEC |
| R3-233912 | Discussion on Partial Reporting and UE Performance Feedback | Intel Corporation |
| R3-233938 | Discussion on Xn impact of LB | Samsung |
| R3-234188 | Left issues related to UE performance feedback collection | Lenovo |
| R3-234204 | (TP to 38.423) Discussion on partial success and post-handover measurement | CATT |
| R3-234280 | (TP for AI/ML BL CR for TS 38.423) Remaining open issues for the Load Balancing use case | Huawei |
| R3-234293 | (TP for AI/ML to BLCR for TS38.423) UE Performance Feedback Configuration | Ericsson, InterDigital, Orange, Deutsche Telekom |
| R3-234294 | (TP for AI/ML to BLCR for TS38.423) Partial reporting of AI-ML assistance data | Ericsson |
| R3-234318 | UE Performance Feedback Configuration | Ericsson, InterDigital, Orange, Deutsche Telekom |
| R3-234329 | Partial reporting of AI-ML assistance data | Ericsson |
| R3-234341 | (TP for TS 38.423) Discussion on AI/ML Load Balancing | Nokia, Nokia Shanghai Bell |
| R3-234377 | (TP to 38.423&38.420) Further discussion on remaining issues on procedures for AI | ZTE |
| R3-234440 | Discussion on AI/ML remaining issues | CMCC |
| R3-234548 | CB:#AIRAN2_LB | Ericsson |
| R3-234689 | (TP for AI/ML to BLCR for TS38.423) UE Performance Feedback Configuration | Ericsson, InterDigital, Orange, Deutsche Telekom |
| 12.2.2.2 | ME and Xn procedures | |
| R3-233913 | Discussion on mobility optimization | Intel Corporation |
| R3-233939 | Discussion on Xn impact of ME | Samsung |
| R3-233974 | Mobility Optimization Outputs | InterDigital |
| R3-233975 | [TP for BL CR 38.423] Handling Additional Mobility Outputs | InterDigital |
| R3-233994 | Discussion on UE Trajectory Feedback for NG-RAN AI/ML | Qualcomm Incorporated |
| R3-234189 | (TP for TS38.423 BLCR) Left issues related to UE trajectory collection by the source gNB | Lenovo, Intel Corporation, ZTE |
| R3-234208 | (TP for 38.423) Support of AI/ML based mobility optimization | CATT |
| R3-234281 | (TP for AI/ML BL CR for TS 38.423) Remaining open issues for the Mobility Enhancements use case | Huawei |
| R3-234295 | Cell based UE trajectory prediction configuration | Ericsson, InterDigital, Orange, Deutsche Telekom |
| R3-234296 | (TP for AIML BLCR for TS 38.423) Cell based UE trajectory prediction exchange | Ericsson, InterDigital, Deutsche Telekom |
| R3-234342 | AI/ML Mobility Optimization | Nokia, Nokia Shanghai Bell |
| R3-234343 | (TP for TS 38.423) AI/ML Mobility Use Case | Nokia, Nokia Shanghai Bell |
| R3-234378 | (TP to 38.423) Discussion on left issues of AI based mobility optimization | ZTE |
| R3-234388 | Discussion on open issue related to measured UE trajectory collection | LG Electronics Inc. |
| R3-234400 | (TP for NR_AIML_NGRAN-Core BL CR for TS 38.423) Discussion on open issue related to measured UE trajectory collection | LG Electronics Inc. |
| R3-234435 | Discussion on Measured UE Trajectory Collection | CMCC |
| R3-234436 | (TP for TS 38.423)Measured UE Trajectory Collection | CMCC |
| R3-234505 | Cell based UE trajectory prediction configuration | Ericsson, InterDigital, Orange, Deutsche Telekom, Orange |
| R3-234506 | (TP for AIML BLCR for TS 38.423) Cell based UE trajectory prediction exchange | Ericsson, InterDigital, Deutsche Telekom, Orange |
| R3-234573 | CB: # AIRAN3_ME | CMCC |
| 12.2.2.3 | ES and Xn procedures | |
| R3-233914 | Discussion on energy efficiency | Intel Corporation |
| R3-233940 | Discussion on Xn impact of ES | Samsung, NTT DOCOMO INC. |
| R3-233941 | TP to 38.423 for predicted energy saving strategy exchanging procedure for AI/ML for NG-RAN | Samsung, Lenovo, Xiaomi, NTT DOCOMO INC., ZTE |
| R3-233993 | Discussion on ES Enhancements for NG-RAN AI/ML | Qualcomm Incorporated |
| R3-234190 | Discussion on issues related to AI based network energy saving | Lenovo |
| R3-234205 | Discussion on the EC metric | CATT |
| R3-234282 | (TP for AI/ML BL CR for TS 38.423) Remaining open issues for the Energy Saving use case | Huawei |
| R3-234297 | (TP for AI/ML BLCR to TS38.423) AI/ML Network Energy Saving | Ericsson |
| R3-234317 | AI/ML Network Energy Saving | Ericsson |
| R3-234344 | Discussion on AI/ML Energy Saving | Nokia, Nokia Shanghai Bell, Deutsche Telekom, Orange |
| R3-234345 | (TP for TS 38.423) AI/ML Energy Saving | Nokia, Nokia Shanghai Bell, Deutsche Telekom, Orange |
| R3-234371 | Further discussion on NG-RAN AIML energy saving | NTT DOCOMO INC.. |
| R3-234379 | (TP to 38.423) Further discussion on AIML based energy saving | ZTE |
| R3-234442 | Further Discussion on Inferred EC for AI/ML for NG-RAN Energy Saving | CMCC |
| R3-234443 | (TP for AI/ML BLCR to TS38.423) AI/ML Network Energy Saving | CMCC |
| R3-234549 | CB:#AIRAN4_ES | Huawei |
| R3-234728 | (TP for AI/ML BLCR to TS38.423) AI/ML Network Energy Saving | Ericsson |
| R3-234752 | (TP for AI/ML BLCR to TS38.423) AI/ML Network Energy Saving | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, ZTE, Samsung |
| 12.2.2.4 | Other interfaces | |
| R3-233942 | Discussion on E1/F1 impact of AI/ML for NG-RAN | Samsung |
| R3-233943 | (CR to 37.483) for AI/ML for NG-RAN | Samsung |
| R3-234191 | (TP for TS37.480 TS38.470) Discussion on E1 F1 interface impact | Lenovo |
| R3-234207 | (TP to 38.473 & 37.483) Discussion on E1AP and F1AP impacts | CATT |
| R3-234283 | (TP for AI/ML BL CR for TS 37.483 and 38.473) On the impact of RAN AI/ML over E1 and F1 interfaces | Huawei |
| R3-234380 | (TP to 38.473&37.483) Consideration on impact of F1E1 impacts | ZTE |
| 12.3 | Others | |
| R3-233989 | Discussion on MDT enhancement for NG-RAN AI/ML | Qualcomm Incorporated |
| R3-234206 | Continuous MDT supporting for AI | CATT |
| R3-234284 | Further discussions on MDT enhancements | Huawei |
| R3-234298 | Continuous MDT proposition | Ericsson, AT&T, InterDigital, Deutsche Telekom |
| R3-234299 | [DRAFT] LS on Continuous MDT | Ericsson, AT&T, InterDigital, Deutsche Telekom |
| R3-234300 | Improved UE selection granularity | Ericsson, AT&T, InterDigital, Deutsche Telekom |
| R3-234301 | [DRAFT] LS on Improved UE selection granularity | Ericsson, AT&T, InterDigital, Deutsche Telekom |
| R3-234346 | Support of continuous MDT measurement collection | Nokia, Nokia Shanghai Bell |
| R3-234347 | Continuous MDT Evaluation | Nokia, Nokia Shanghai Bell |
| R3-234381 | Discussion on MDT enhancement for continuous AI-ML related information | ZTE, Lenovo, Samsung |
| R3-234382 | (TP to TS38.413) MDT Enhancements for continuous data collection | ZTE, Lenovo, Samsung |
| R3-234383 | [DRAFT] LS on the MDT enhancement to support continuous AI-ML related information reporting from UE | ZTE |
| R3-234550 | CB:#AIRAN5_MDT | Nokia |
| 13.1 | General | |
| R3-233750 | (BLCR to 38.413) Support for mobile IAB | Nokia, Nokia Shanghai Bell |
| R3-233788 | Introduction of Mobile TRP | Ericsson, Xiaomi, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-233801 | Support for mobile TRP Location Information | Xiaomi, Ericsson, Qualcomm Inc., CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-233806 | Support of mobile TRP location information | Ericsson, Xiaomi, Qualcomm, CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-233889 | Updated workplan for Rel-18 mobile IAB | Qualcomm Inc. (Rapporteur) |
| R3-233890 | (Draft Reply LSs) Discussion on Reply LSs to RAN2 and SA2 | Qualcomm Inc. |
| R3-234546 | Offline discussion on Mobile IAB | Qualcomm |
| R3-234803 | (BL CR to 38.413) Support for mobile IAB | Nokia, Nokia Shanghai Bell |
| R3-234804 | (BL CR to 38.473): Support for mobile IAB | Ericsson, Xiaomi, Qualcomm, CATT, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-234831 | (BL CR to 38.401) Support for mobile IAB | Huawei |
| R3-234832 | (BL CR to 38.470) New F1 setup | ZTE |
| 13.2 | Support IAB-node mobility | |
| R3-233837 | Discussion on IAB-node mobility | CANON Research Centre France |
| R3-233881 | (TP for Mobile IAB BL CR TS38.401) Discussion on IAB-node mobility and integration | Fujitsu |
| R3-233892 | (TP to TS 38.401) BL ST2 procedures for mobile IAB | Qualcomm Inc. |
| R3-233893 | Open issues for mobile IAB topology adaptation | Qualcomm Inc. |
| R3-233967 | (TP for Mobile IAB BL CR for TS 38.413 38.423 38.473) Inter-donor migration in mobile IAB scenario | ZTE |
| R3-234009 | (TP for Mobile IAB TS38.413 BL CR) Discussion on Support IAB-node mobility | Nokia, Nokia Shanghai Bell |
| R3-234035 | (TP for mIAB BL CR for TS 38.401) Migration Procedure for Mobile IAB-Nodes | Ericsson |
| R3-234047 | Discussion on DU migration | Samsung |
| R3-234048 | Discussion on multiple partial migration | Samsung |
| R3-234141 | (TP for NR_mobile_IAB BL CRs for TS 38.401/ 38.473) Support of mobility for mobile IAB | Huawei |
| R3-234169 | Discussion on mobile IAB-node inter-donor topology adaptation | Lenovo |
| R3-234252 | Discussion on IAB-node mobility | Xiaomi |
| R3-234259 | Discussion on XnAP and F1AP enhancements for mobile IAB | MITRE Corporation |
| R3-234305 | (TPs to TS38.473/TS38.413 BL CR) Consideration on support IAB-node mobility | CATT |
| R3-234580 | Summary of Offline discussion(*canceled allocation) | Qualcomm |
| R3-234592 | (TPs to TS 38.401) Mobile IAB-MT migration via Xn handover | Qualcomm Incorporated |
| R3-234593 | (TP for Mobile IAB BL CR for TS 38.413) Introducing of mobile IAB indication and mobile IAB authorization information in NGAP | ZTE |
| R3-234594 | (TP for NR_mobile_IAB BL CR for TS 38.473) New F1 setup | Huawei |
| R3-234595 | (TP for Mobile IAB BL CR for TS 38.473) Transfer of gNB-ID of mIAB-MT's CU | ZTE |
| R3-234707 | (TP for NR_mobile_IAB BL CR for TS 38.470) New F1 setup | Nokia, Nokia Shanghai Bell |
| R3-234751 | (TPs to TS 38.401) Mobile IAB-MT migration via Xn handover | Qualcomm Incorporated |
| R3-234753 | (TP for Mobile IAB BL CR for TS 38.473) Transfer of gNB-ID of mIAB-MT's CU | ZTE |
| R3-234754 | (TP for NR_mobile_IAB BL CR for TS 38.470) New F1 setup | Nokia, Nokia Shanghai Bell |
| R3-234755 | (TP for Mobile IAB BL CR for TS 38.413) Introducing of mobile IAB indication and mobile IAB authorization information in NGAP | ZTE |
| R3-234756 | (TP for NR_mobile_IAB BL CR for TS 38.473) New F1 setup | Huawei |
| 13.3 | Mobility Enhancements | |
| R3-233824 | Discussion on mobility enhancements for mobile-IAB | KT Corp. |
| R3-233968 | (TP for Mobile IAB BL CR for TS 38.473) Enhancements to IAB node migration in mobile IAB scenario | ZTE |
| R3-234010 | Discussion on IAB configuration and Mobility Enhancements | Nokia, Nokia Shanghai Bell |
| R3-234036 | IAB-Node Mobility Enhancements | Ericsson |
| R3-234049 | Discussion on mobility enhancements | Samsung |
| R3-234142 | (TP for NR_mobile_IAB BL CR for TS 38.423): Mobility enhancement for mobile IAB | Huawei |
| R3-234170 | Mobility enhancements for mobile IAB-node and its served UE | Lenovo |
| R3-234253 | Discussion on mobility enhancement | Xiaomi |
| R3-234306 | Enhancements for mobility IAB | CATT |
| 13.4 | Mitigation of interference | |
| R3-233838 | PCI Collision Avoidance with Mobile IAB | CANON Research Centre France |
| R3-233969 | Discussion on PCI collision avoidance for mobile IAB | ZTE |
| R3-234011 | Mobile IAB interference mitigation | Nokia, Nokia Shanghai Bell |
| R3-234037 | PCI Collision Avoidance for Mobile IAB-Nodes | Ericsson |
| R3-234050 | Discussion on mitigation of interference | Samsung |
| R3-234171 | PCI collision mitigation of mobile IAB-node mobility | Lenovo |
| R3-234307 | Discussion on interference mitigation | CATT |
| 13.5 | Others | |
| R3-233713 | LS on UE RACH-less handover for mobile IAB | RAN2(Huawei) |
| R3-233717 | LS on CAG solution for mobile IAB | RAN2(Ericsson) |
| R3-233730 | LS On IAB-node De-authorization handling | SA2(Ericsson) |
| R3-233891 | Draft Reply LS on VMR | Qualcomm Inc. |
| R3-233970 | (TP for Mobile IAB BL CR TS38.473) Enhancements on positioning and additional ULI for mobile IAB | ZTE, Xiaomi |
| R3-234012 | Discussion on incoming LS | Nokia, Nokia Shanghai Bell |
| R3-234038 | (TP for mIAB BL CR for TS 38.470) Discussion of SA2 FS_VMR Solutions | Ericsson |
| R3-234039 | Discussion and Draft Reply LS on Mobile IAB-node De-authorization Handling | Ericsson |
| R3-234143 | (TP for NR_mobile_IAB BL CR for TS 38.455): Positioning enhancement on uplink E-CID measurement for mobile TRP | Huawei, Ericsson, Xiaomi |
| R3-234144 | (TP for NR_mobile_IAB BL CR for TS 38.473): Positioning enhancement on uplink E-CID measurement for mobile TRP | Huawei, Ericsson, Xiaomi |
| R3-234145 | Discussion on IAB-node De-authorization handling | Huawei |
| R3-234146 | Support of RACH-less HO for mobile IAB | Huawei |
| R3-234147 | [draft] Reply LS on UE RACH-less handover for mobile IAB | Huawei |
| R3-234168 | Discussion on IAB-node de-authorization handling | Lenovo |
| R3-234251 | (TP for TS 38.423 support of de-authorization for mobile IAB) Discussion on authorization and additional ULI | Xiaomi |
| R3-234455 | Enhancements for IAB-node mobility and onboard UEs | AT&T |
| 14.1 | General | |
| R3-233743 | (BLCR to 38.401) for L1L2Mob | Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-233759 | (BL CR to TS 38.423) Introduction of SCG Selective Activation | Huawei |
| R3-233766 | (BLCR to 38.473) Additions for L1/L2 triggered mobility | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation |
| R3-233776 | (BLCR to 37.340) Introduction of CHO with SCG(s) | CATT |
| R3-234563 | (BLCR to 37.340) Introduction of CHO with SCG(s) | CATT |
| R3-234799 | (BL CR to 37.340) Introduction of CHO with SCG(s) | CATT |
| R3-234800 | (BLCR to 38.401) for L1L2Mob | Huawei, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-234801 | (BL CR to TS 38.423) Introduction of Subsequent CPAC | Huawei, ZTE |
| R3-234802 | (BLCR to 38.473) Additions for L1/L2 triggered mobility | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Intel Corporation, ZTE |
| R3-234830 | (BL CR to 38.423) Introduction of CHO with SCG(s) | Lenovo, Ericsson, Huawei |
| 14.2 | Signaling Support for L1/L2 based Inter-Cell Mobility | |
| R3-233709 | LS on beam application time, contents of cell switch command, TCI state activation and UE based TA measurement for LTM | RAN1(Fujitsu/Mediatek/CATT) |
| R3-233719 | LS on Early TA and RACH-less | RAN2(Ericsson) |
| R3-233720 | LS on L1 measurements for LTM | RAN2(Ericsson) |
| R3-233827 | TP (BL CR TS 38.401) L1/2 Triggered Mobility (LTM) Procedures | Nokia, Nokia Shanghai Bell |
| R3-233828 | TP (BL CR TS 38.473) Additional Implications to L1/2 Triggered Mobility (LTM) | Nokia, Nokia Shanghai Bell |
| R3-233840 | (TP to Mob_enh2 BL CR TS38.401) Discussion on L1/L2 based Inter-cell Mobility | Samsung Beijing |
| R3-233869 | Rel-18 LTM issues | NEC |
| R3-233870 | (TP to TS 38.473 on LTM) co-existence between LTM and L3 mobility | NEC |
| R3-233886 | (TP for L1L2Mob BLCR for TS 38.401) Reference configuration and Target Configuration ID in LTM | Google Inc. |
| R3-233887 | (TP for L1L2Mob BLCR for TS 38.473) Reference configuration and Target Configuration ID in LTM | Google Inc. |
| R3-233888 | (TP for L1L2Mob BL CR for TS 38.473) UE Context identification | Google Inc. |
| R3-233905 | (TP for LTM BL CR to TS 38.401) Solutions for LTM | Ericsson |
| R3-233906 | (TP for LTM BL CR to TS 38.473) F1AP impacts for LTM | Ericsson |
| R3-233984 | Signalling Support for LTM | Qualcomm Incorporated |
| R3-234040 | Resource management at gNB-DU for LTM | Rakuten Symphony |
| R3-234041 | Intra gNB CU-UP relocation during LTM | Rakuten Symphony |
| R3-234074 | (TP for L1L2Mob BLCR for TS 38.401): Discussion on RAN3 impacts from the incoming LSs | Huawei |
| R3-234075 | (TP for L1L2Mob BLCR for TS 38.473): L1/L2 Mobility | Huawei |
| R3-234165 | Discussion on L1L2 based inter-cell mobility | Lenovo |
| R3-234166 | (TP to TS 38.401 & TS 38.470) Support of L1L2 based inter-cell mobility | Lenovo |
| R3-234201 | (TP for BLCR of 38.401)Further consideration about LTM execution procedure | CATT |
| R3-234202 | (TP for 38.473 BLCR) Further consideration about candidate cell configuration | CATT |
| R3-234348 | Discussions on stage-3 and inter-DU LTM | LG Electronics Inc. |
| R3-234349 | (TP for LTM BL CR for TS 38.473) | LG Electronics Inc. |
| R3-234368 | Further discussion on LTM | NTT DOCOMO INC.. |
| R3-234446 | (TP to TS 38.401) L1/L2 based Inter-Cell Mobility | CMCC |
| R3-234447 | Discussion on L1L2 based Inter-Cell Mobility | CMCC |
| R3-234459 | (TP for LTM BL CR to TS 38.473) Discussion on L1L2 triggered mobility | ZTE |
| R3-234460 | TP for LTM BL CR to TS 38.401 | ZTE |
| R3-234574 | CB:#MobilityEhn_L1L2Mobility | Huawei |
| R3-234642 | (TP for L1L2Mob BLCR for TS 38.401): Inter-DU LTM procedure update | Huawei, Nokia, Nokia Shanghai Bell, ZTE, LG Electronics, Ericsson |
| R3-234661 | (TP to TS 38.473 on LTM) co-existence between LTM and L3 mobility | NEC, Nokia, Nokia Shanghai Bell, Huawei, Lenovo, LG Electronics, ZTE, Google |
| R3-234690 | (TP for LTM BL CR to TS 38.473) F1AP impacts for LTM | Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, Lenovo, LG Electronics |
| R3-234709 | TP for LTM BL CR to TS 38.401 | ZTE, Nokia, Nokia Shanghai Bell, LG Electronics, Huawei, Ericsson |
| R3-234757 | TP for LTM BL CR to TS 38.401 | ZTE, Nokia, Nokia Shanghai Bell, LG Electronics, Huawei, Ericsson, CMCC |
| R3-234758 | (TP for L1L2Mob BLCR for TS 38.401): Inter-DU LTM procedure update | Huawei, Nokia, Nokia Shanghai Bell, ZTE, LG Electronics, Ericsson, CMCC |
| R3-234759 | (TP to TS 38.473 on LTM) co-existence between LTM and L3 mobility | NEC, Nokia, Nokia Shanghai Bell, Huawei, Lenovo, LG Electronics, ZTE, Google, Samsung, CMCC |
| R3-234760 | (TP for LTM BL CR to TS 38.473) F1AP impacts for LTM | Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, Lenovo, LG Electronics, CMCC |
| 14.3 | Support CHO in NR-DC | |
| R3-233818 | (TP for CHO with NR-DC to TS 38.423, TS37.340): Early data forwarding optimization for CHO with SCG procedure | ZTE |
| R3-233834 | [TPs to TS38423, TS37483 and TS37340, CHO with NRDC] Continuation of the discussions on enhancements for CHO with MR-DC | Nokia, Nokia Shanghai Bell |
| R3-233907 | (TP to TS 37.340 and 38.423 BL CRs) CHO with candidate SCG(s) | Ericsson |
| R3-233954 | (TP to BLCR TS38.423) Considerations on CHO in NR-DC | Samsung |
| R3-233982 | CHO with multiple candidate SCGs | Qualcomm Incorporated |
| R3-234084 | (TPs to TS 37.340 and 38.423 BL CRs) avoid multiple data forwarding paths | Huawei, Samsung, Lenovo, Qualcomm Incorporated |
| R3-234085 | (TPs for TS 37.340, 38.423 BLCRs) Other CHO related aspects | Huawei |
| R3-234167 | Discussion on CHO in NR-DC | Lenovo |
| R3-234350 | Discussion on signaling support for CHO with SCGs (TP for TS 38.423) | LG Electronics Inc. |
| R3-234394 | TP to BLCR for 38.423 on CHO with SCG and multiple SCGs | CATT |
| R3-234575 | CB:#MobilityEhn_CHO | Samsung |
| R3-234631 | (TP to TS 37.340 BLCR on CHO with SCG) Avoid multiple data forwarding paths | Nokia, Nokia Shanghai Bell |
| R3-234632 | (TP to TS 37.340 BLCR on CHO with SCG) Support of CHO with multiple SCGs | ZTE, Samsung, Huawei, LG Electronics, Ericsson, Nokia, Nokia |
| R3-234633 | (TP to TS 38.423 BLCR on CHO with SCG) Support of CHO with multiple SCGs | Ericsson |
| R3-234634 | (TP to TS 38.423 BLCR on CHO with SCG) Avoid multiple data forwarding paths | Huawei |
| R3-234705 | (TP to 38.423 BL CR) CHO with candidate SCG(s) | Ericsson |
| R3-234734 | (TP to TS 38.423 BLCR on CHO with SCG) Avoid multiple data forwarding paths | Huawei, LG Electronics, Samsung, ZTE, Ericsson |
| R3-234761 | (TP to TS 38.423 BLCR on CHO with SCG) Support of CHO with multiple SCGs | Ericsson, Nokia, Nokia Shanghai Bell, LG Electronics, ZTE, Samsung, CATT |
| 14.4 | Others | |
| R3-233835 | Considerations on the indication of Selective Activation and collateral problems that must be addressed to enable the feature. | Nokia, Nokia Shanghai Bell |
| R3-233871 | Discussion on Selective Activation of the cell of groups | NEC |
| R3-233872 | (TP to TS38.423 BL CR) Selective Activation of the cell of groups | NEC |
| R3-233885 | (TPs for SCG Selective Activation BLCR for TS 38.423 & TS 38.473) Reference SCG configuration | Google Inc. |
| R3-233908 | (TP to TS 38.423 BL CR) Subsequent CPAC | Ericsson |
| R3-233983 | SCG Selective Activation in NR-DC | Qualcomm Incorporated |
| R3-234000 | Discussion on subsequent CPAC procedures | China Telecommunication |
| R3-234001 | (TP to BL CRs of 38.423/38.473) On support of subsequent CPAC procedures | China Telecommunication |
| R3-234086 | (TP to TS 38.423 BLCR) Consideration on Subsequent CPAC | Huawei |
| R3-234192 | (TP for TS 38.473) On Subsequent CPAC | Lenovo |
| R3-234369 | Security issue on selective activation | NTT DOCOMO INC.. |
| R3-234384 | Discussion on selective activation of the cell groups | Samsung |
| R3-234395 | Discussion on NR-DC with selective activation of the cell groups | CATT |
| R3-234461 | (TP for TS 38.423 BL CR) Discussion on support of subsequent CPAC | ZTE |
| R3-234462 | (Subsequent CPAC BL CR to TS 37.340) Introduction of subsequent CPAC | ZTE, China Telecom, Huawei, China Unicom |
| R3-234576 | CB:#MobilityEhn_S-CPAC | ZTE |
| R3-234706 | (TP for TS 38.423 BLCR) Correction on Subsequent CPAC naming | Lenovo |
| R3-234708 | (Subsequent CPAC BL CR to TS 37.340) Introduction of subsequent CPAC | ZTE, China Telecom, Huawei, China Unicom, LG Electronics, Samsung, Ericsson |
| R3-234764 | (TP for TS 38.423 BLCR) Correction on Subsequent CPAC naming | Lenovo, ZTE, Ericsson, Nokia, Nokia Shanghai Bell |
| 15.1 | General | |
| R3-233741 | Support of MBS enhancement | Ericsson, Nokia, Nokia Shanghai Bell |
| R3-233749 | Support of MBS enhancement | CATT, Nokia, Nokia Shanghai Bell |
| R3-233765 | (BLCR to 38.473) Support of MBS enhancement | Samsung, Nokia, Nokia Shanghai Bell |
| R3-233782 | (BL CR to TS 38.300) Introduction of NR MBS enhancements | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Ericsson, Lenovo |
| R3-233791 | (BLCR to 38.401) Introduction of NR MBS enhancements | Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo |
| R3-233803 | (BLCR to 38.470) Multicast Reception for RRC_INACTIVE state UEs | Lenovo, Huawei, Nokia, Nokia Shanghai Bell |
| R3-234615 | Summary of unofficial offline Discussion on Rel-18 MBS | CATT |
| R3-234635 | (BL CR to TS 38.423) Introduction of NR MBS enhancements | Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm, Huawei, CATT, Samsung |
| R3-234636 | Support of MBS enhancement | CATT, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm, Huawei, CATT, Samsung |
| R3-234637 | (BL CR to TS 38.473) Introduction of NR MBS enhancements | Samsung, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm Incorporated, Huawei, CATT |
| R3-234638 | (BL CR to TS 38.470) Introduction of NR MBS enhancements | Lenovo, Huawei, Nokia, Nokia Shanghai Bell |
| R3-234639 | (BL CR to TS 38.300) Introduction of NR MBS enhancements | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Ericsson, Lenovo |
| R3-234640 | (BLCR to 38.401) Introduction of NR MBS enhancements | Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, ZTE, CATT, Samsung |
| R3-234795 | (BL CR to 38.300) Introduction of NR MBS enhancements | Nokia, Nokia Shanghai Bell, Huawei, ZTE, Ericsson, Lenovo, Qualcomm Incorporated, CATT, Samsung |
| R3-234796 | (BL CR to 38.401) Introduction of NR MBS enhancements | Huawei, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, Lenovo, ZTE, CATT, Samsung |
| R3-234797 | (BL CR to TS 38.413) Introduction of NR MBS enhancements | CATT, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm, Huawei, Samsung, Ericsson |
| R3-234798 | (BL CR to TS 38.473) Introduction of NR MBS enhancements | Samsung, Nokia, Nokia Shanghai Bell, ZTE, Qualcomm Incorporated, Huawei, CATT |
| R3-234829 | (BL CR to 37.483) Introduction of NR MBS enhancements | ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Inc., CATT, Huawei, Ericsson, CMCC, Samsung |
| 15.2 | Support for MBS reception in RAN sharing scenarios | |
| R3-233852 | (TP for TS 38.470, 37.483, 38.473) Resolution of RAN sharing open points | Nokia, Nokia Shanghai Bell |
| R3-233948 | (TP for BLCR TS37.483) Discussion on MBS RAN sharing | Samsung |
| R3-233978 | Stage-2 CR for Introducing MBS RAN Sharing for OAM based solution. | Qualcomm Incorporated, Huawei, Nokia, Nokia Shanghai Bell |
| R3-233979 | Support of MBS in RAN sharing scenarios | Qualcomm Incorporated |
| R3-234089 | (TPs to MBS BL CRs) MBS reception in RAN sharing scenario | Huawei, CBN |
| R3-234184 | Remaining issues of supporting MBS reception in RAN Sharing | Lenovo |
| R3-234211 | (TP to TS 38.413, 38.473) Network sharing for MBS Broadcast | ZTE |
| R3-234233 | Further thoughts on MBS reception for RAN sharing scenarios | Ericsson |
| R3-234247 | Discussion on efficient MBS reception in RAN sharing scenario | CATT,CMCC,CBN |
| R3-234697 | (TP for BL CR for 38.300) Update of MBS RAN sharing solution | ZTE, Huawei, Ericsson, CATT, Nokia, Nokia Shanghai Bell, Samsung, CMCC, Qualcomm |
| R3-234698 | (TP for BL CR for 38.401) Update of MBS RAN sharing solution | CATT |
| R3-234699 | (TP for BL CR for 38.410) Update of MBS RAN sharing solution | Qualcomm Inc, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CATT, Huawei |
| R3-234700 | (TP for BL CR for 38.413) Update of MBS RAN sharing solution | Huawei, Nokia, Nokia Shanghai Bell, CATT, ZTE, Ericsson, Samsung, Qualcomm Incorporated |
| R3-234701 | (TP for BL CR for 38.473) Update of MBS RAN sharing solution | Samsung |
| R3-234702 | (TP for TS 37.483) Update of MBS RAN Sharing Solution | Nokia |
| R3-234763 | (*cancelled allocation) | Huawei |
| R3-234765 | (TP for BL CR for 38.401) Update of MBS RAN sharing solution | CATT, ZTE, Huawei, Nokia, Nokia shanghai Bell, Ericsson, Qualcomm, CMCC, CBN, Samsung |
| R3-234766 | (TP for TS 37.483) Update of MBS RAN Sharing Solution | Nokia, Nokia Shanghai Bell, Qualcomm Inc., CATT, Huawei, ZTE, Ericsson, CMCC, Samsung |
| R3-234773 | (*cancelled allocation) | CATT, ZTE, Huawei, Nokia, Nokia shanghai Bell, Ericsson, Qualcomm, CMCC, CBN, Samsung |
| R3-234828 | (BL CR to 38.410) Update of MBS RAN sharing solution | Qualcomm Inc, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CATT, Huawei |
| 15.3 | Support for RRC_INACTIVE state | |
| R3-233853 | (TP for TS 38.300, TS 38.423) Resolution of open points for Reception in RRC Inactive State | Nokia, Nokia Shanghai Bell |
| R3-233949 | (TP for BLCR TS38.473) Discussion on MBS reception by inactive state UE | Samsung |
| R3-233980 | Enhancements to support Multicast reception by UEs in RRC_INACTIVE state | Qualcomm Incorporated |
| R3-234090 | (TPs to MBS BL CRs) Multicast Reception for RRC_INACTIVE state UEs | Huawei, CBN |
| R3-234183 | Discussion on multicast reception in RRC_INACTIVE | Lenovo |
| R3-234212 | (TP to TS 38.413, 38.473) Multicast reception in RRC_INACTIVE | ZTE |
| R3-234234 | Further thoughts on support for RRC_INACTIVE | Ericsson |
| R3-234246 | Discussion on Multicast over Inactive | CATT,CBN |
| R3-234450 | Multicast Reception in RRC_INACTIVE state | CMCC |
| R3-234703 | (TP for BLCR for 38.473) Update of MBS RRC_INACTIVE reception | Ericsson, Huawei, Samsung, Nokia, Nokia Shanghai Bell, CATT, ZTE, Qualcomm, CMCC |
| R3-234704 | (TP for BLCR for 38.401) Update of MBS RRC_INACTIVE reception | CMCC, Huawei, CATT, ZTE, Ericsson, Nokia, Nokia shanghai Bell, Qualcomm, Samsung |
| R3-234767 | (TP for BLCR for 38.473) Update of MBS RRC_INACTIVE reception | Ericsson, Huawei, Samsung, Nokia, Nokia Shanghai Bell, CATT, ZTE, Qualcomm, CMCC |
| 16.1 | General | |
| R3-233745 | (BLCR to 38.401) Introduction of NR SL relay enhancements | LG Electronics |
| R3-233754 | (BLCR to 38.413) Support for NR Sidelink Relay Enhancements | Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson, CMCC, ZTE, Samsung, LG Electronics, Huawei |
| R3-233763 | (BLCR to 38.423) Support NR Sidelink Relay Enhancements | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, Samsung, Huawei, CATT, LG Electronics, CMCC |
| R3-233769 | (BLCR to 38.473) Support for NR Sidelink Relay Enhancements | Huawei, CMCC, LGE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-233787 | Support of SL relay enhancement in TS38.300 | CMCC, CATT, Samsung, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, ZTE |
| R3-234577 | (BLCR to 38.300) Support of SL relay enhancements | CMCC, CATT, Samsung, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, ZTE |
| R3-234817 | (BL CR to 38.300) Support of SL relay enhancements | CMCC, CATT, Samsung, China Telecom, Nokia, Nokia Shanghai Bell, Ericsson, LG Electronics, ZTE, Huawei |
| R3-234818 | (BL CR to 38.413) Support for NR Sidelink Relay Enhancements | Nokia, Nokia Shanghai Bell, Qualcomm, Ericsson, CMCC, ZTE, Samsung, LG Electronics, Huawei |
| R3-234819 | (BLCR to 38.423) Support NR Sidelink Relay Enhancements | Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, Samsung, Huawei, CATT, LG Electronics, CMCC |
| R3-234820 | (BL CR to 38.473) Support for NR Sidelink Relay Enhancements | Huawei, CMCC, LGE, CATT, Ericsson, Nokia, Nokia Shanghai Bell, Samsung, ZTE |
| R3-234835 | (BLCR to 38.470) Support of NR SL relay enhancements | ZTE, CAICT, China Telecom, CATT, LG Electronics, Ericsson, Huawei |
| 16.2 | Support Relay and Remote UE Authorization | |
| R3-233716 | Reply LS on ProSe Authorization information related to UE-to-UE Relay operation | RAN2(ZTE) |
| R3-233725 | Reply LS to SA2 on authorization for multi-path Scenario 2 | SA2(LGE) |
| R3-233882 | Authorization for U2U relay | ZTE |
| R3-234667 | (TP for 38.473) Authorization for U2U relay | Huawei |
| R3-234674 | (TP for 38.423) Authorization for U2U relay | Ericsson |
| 16.3 | Support Service Continuity Enhancements | |
| R3-233879 | Discussion on remaining issue for service continuity | NEC |
| R3-233902 | (TP for BLCR 38.413, 38.423) Inter-gNB mobility | Huawei |
| R3-233909 | (TP for SL Relay BL CR to TS 38.423) Inter-gNB Service Continuity for L2 U2N Relay | Ericsson |
| R3-233998 | Discussion on service continuity and U2U authorization | China Telecommunication |
| R3-234013 | (TP for TS38.300 BL CR) Discussion on Support Service Continuity Enhancements | Nokia, Nokia Shanghai Bell |
| R3-234026 | Another issue on DL lossless delivery | Samsung |
| R3-234113 | (TP for SL relay 38.300, 38.413, 38.423 and 38.473) Discussion on Support Service Continuity Enhancements | CATT |
| R3-234437 | (TP for SL relay to TS 38.300) Considerations on service continuity | CMCC, Ericsson, CATT, Huawei, China Telecom, NEC, Samsung |
| R3-234438 | Discussion on downlink lossless delivery | CMCC |
| R3-234453 | Remaining open issues for service continuity enhancement | LG Electronics |
| R3-234578 | CB:#SLRely_Dllosslessdelivery | LG |
| R3-234673 | (TP for SL relay to TS 38.300) Considerations on service continuity | CMCC, Ericsson, CATT, Huawei, China Telecom, NEC, Samsung |
| 16.4 | Multi-path Support | |
| R3-233712 | LS to RAN3 on mode 1 scheduling in inter-DU multi-path case | RAN2(NEC) |
| R3-233880 | Discussion on mode 1 RA for U2N remote UE under multi-path relay | NEC, TCL, ZTE, OPPO, LG Electronics, CMCC, Samsung |
| R3-233883 | Discussion on multi-path relay support | ZTE |
| R3-233903 | (TP for BLCR 38.413, 38.423, 38.473) Multi-path relay and U2U relay | Huawei |
| R3-233910 | (TP for SL Relay to TS 38.470) Multi-path for Sidelink Relay | Ericsson |
| R3-234008 | (TP to TS 38.473) Discussion on multi-path for sidelink relay | China Telecommunication |
| R3-234014 | discussion on the support for multi-path | Nokia, Nokia Shanghai Bell |
| R3-234027 | Remaining issues on multipath | Samsung |
| R3-234114 | (TP for SL relay 38.401 and 38.473) Discussion on Multi-path Support for SL relay | CATT |
| R3-234196 | (BLCR to 38.470) Support of NR SL relay enhancements | ZTE, CAICT, China Telecom, CATT, LG Electronics |
| R3-234439 | (TP for SL relay to TS 38.401) Considerations on multi-path | CMCC |
| R3-234454 | Further consideration on U2U relay and multi-path support | LG Electronics |
| R3-234579 | CB:#SLRelay_MP | Ericsson |
| R3-234692 | (TP for 38.470) SL relay Enhancement | ZTE, CAICT, China Telecom, CATT, LG Electronics, Ericsson, Huawei |
| R3-234693 | (TP for BL CR 38.413) Support ProSe Authorization information for UE-to-UE Relay operation | Nokia, Nokia Shanghai Bell |
| 17.1 | General | |
| R3-233751 | NGAP BLCR on NTN Functionality | Nokia, Nokia Shanghai Bell, Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes Network Systems, Huawei, Lockheed Martin, Intelsat, ESA, Samsung, Qualcomm Incorporated |
| R3-233784 | (BLCR to 38.300) Stage 2 BL CR for NR NTN | Ericsson, CATT, Thales, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-233799 | XnAP BLCR on NTN Functionality | Huawei, Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT, Hughes, EchoStar, CMCC |
| R3-233842 | R18 WI NR-NTN-enh work plan at RAN1, 2 and 3 | THALES |
| R3-234508 | (BLCR to 38.300) Stage 2 BL CR for NR NTN | Ericsson, CATT, Thales, Huawei, Samsung, ZTE, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
| R3-234659 | (BLCR to 38.413) BL CR for NR NTN | Nokia, Nokia Shanghai Bell, Ericsson, Thales, ZTE, Omnispace, TTP, CATT, Hughes Network Systems, Huawei, Lockheed Martin, Intelsat, ESA, Samsung, Qualcomm Incorporated |
| R3-234660 | (BLCR to 38.423) BL CR for NR NTN | Huawei, Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT, Hughes, EchoStar, CMCC |
| R3-234782 | (BL CR to 38.423) for NR NTN | Huawei, Ericsson, Thales, ZTE, Omnispace, TTP, Nokia, Nokia Shanghai Bell, CATT, Hughes, EchoStar, CMCC |
| 17.2 | Support Mobility and Service Continuity Enhancements | |
| R3-233721 | LS on common signalling in (C)HO | RAN2(OPPO) |
| R3-233876 | Further discussion on TAC exchange over Xn for NR NTN | NEC |
| R3-233987 | [Draft] Reply LS on Common Signaling in (C)HO | Qualcomm Incorporated |
| R3-233999 | Discussion on NTN Service Continuity Enhancements | China Telecommunication |
| R3-234015 | (TP for TS38.300 BL CR) Discussion on Support Mobility and Service Continuity Enhancements | Nokia, Nokia Shanghai Bell |
| R3-234028 | Remaining issue on service continuity enhancement for NTN | Samsung |
| R3-234057 | Further discussion on mobility issue for NR NTN | ZTE |
| R3-234058 | [DRAFT] Reply LS on common signalling in (C)HO | ZTE |
| R3-234100 | Further discussion on multiple TACs | Huawei |
| R3-234101 | Discussion on common signalling in CHO | Huawei |
| R3-234158 | Time Margin for CHO in NR NTN | Ericsson, Thales, ESA |
| R3-234159 | Time Margin for CHO in NR NTN - XnAP Impact | Ericsson, ESA, Thales |
| R3-234160 | Common Signaling in (C)HO | Ericsson LM |
| R3-234161 | [DRAFT] Reply LS on Common Signaling in (C)HO | Ericsson LM |
| R3-234358 | Consideration on support of common signalling in (C)HO | CATT,OPPO |
| R3-234359 | Discussion on mobility leftover issues | CATT |
| R3-234360 | (TP to BL CR for TS 38.423) Correction to time based CHO | CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-234370 | Xn enhancement for NR NTN mobility | NTT DOCOMO INC.. |
| R3-234662 | Reply LS | nn |
| R3-234664 | Reply LS on Common Signaling in ©HO | RAN3(Qualcomm) |
| 17.3 | Network verified UE location | |
| R3-233988 | Discussion on TRP Information for NR NTN | Qualcomm Incorporated |
| R3-234016 | Discussion on UE location verification | Nokia, Nokia Shanghai Bell |
| R3-234102 | Further discussion on network verified UE location | Huawei, Ericsson, CATT, Samsung |
| R3-234103 | (TP to 38.300) OAM Requirements for UE Location Verification | Huawei, Ericsson, CATT |
| R3-234124 | OAM Requirements for UE Location Verification | Ericsson, CATT, Huawei |
| R3-234125 | [DRAFT] Reply LS on Latency impact for NTN verified UE location | Ericsson, CATT, Huawei |
| R3-234361 | Consideration on OAM requirements for UE location verification | CATT,Ericsson, Huawei,Samsung |
| 18.1 | General | |
| R3-233771 | (BLCR to 36.300) IoT NTN enhancements | ZTE, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson |
| R3-233773 | (BLCR) Support for IoT NTN enhancements | Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson, Huawei, ZTE |
| R3-233774 | (BLCR) X2AP CR on IoT NTN Functionality | Huawei, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, CMCC, Ericsson, Samsung |
| R3-234677 | (BLCR to 36.413) IoT NTN enhancements | Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson, Huawei, ZTE |
| R3-234678 | (BLCR to 36.423) IoT NTN enhancements | Huawei, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, CMCC, Ericsson, Samsung |
| R3-234779 | (BL CR to 36.300) IoT NTN enhancements | ZTE, Huawei, Nokia, Nokia Shanghai Bell, CATT, Ericsson |
| R3-234780 | (BL CR to 36.413) IoT NTN enhancements | Nokia, Nokia Shanghai Bell, CATT, Thales, Ericsson, Huawei, ZTE |
| R3-234781 | (BLCR to 36.423) IoT NTN enhancements | Huawei, CATT, Nokia, Nokia Shanghai Bell, Qualcomm, ZTE, CMCC, Ericsson, Samsung |
| 18.2 | Support discontinuous coverage | |
| R3-234017 | (TP for BL CR 36.300 and 36.413) on support X2-CHO and S1-HO with time-based trigger condition | Nokia, Nokia Shanghai Bell |
| R3-234059 | Further discussion on discontinuous coverage issue for IoT NTN | ZTE |
| R3-234105 | Time-Based HO and IoT NTN - Stage 2 Impacts | Ericsson, CATT, ESA, Huawei |
| R3-234106 | Time-Based HO for IoT NTN - S1AP Impacts | Ericsson, Huawei, CATT, ESA |
| R3-234107 | Time Margin for CHO in IoT NTN - X2AP Impact | Ericsson, Inmarsat, ESA |
| R3-234200 | (TP for BL CR IoT NTN TS36.423) Correction for Time based CHO | CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei |
| R3-234219 | (TP to BL CRs, 36.300, 36.423) Alignment with NR NTN | Huawei, Ericsson |
| R3-234679 | (TP to BL CR 36.423) Alignment with NR NTN | Huawei, Ericsson |
| R3-234680 | Further discussion on discontinuous coverage issue for IoT NTN | ZTE |
| R3-234768 | Further discussion on discontinuous coverage issue for IoT NTN | ZTE |
| 19.1 | General | |
| R3-233809 | (BLCR) Draft CR to 38.300 on NR support for UAV | Nokia, Nokia Shanghai Bell, Huawei, Intel Corporation, ZTE, Ericsson, Samsung, CATT, Qualcomm, Deutsche Telekom, NEC |
| R3-233810 | Introduction of Aerial authorization information | Ericsson, AT&T, NTT DOCOMO INC, Qualcomm Incorporated, Intel Corporation, Samsung, NEC, Nokia, Nokia Shanghai Bell, Huawei, ZTE, CATT |
| R3-233811 | NR support for UAV over Xn | Huawei, China Unicom, China Telecom, CATT, Intel Corporation, ZTE, Ericsson, Qualcomm, Nokia, Nokia Shanghai Bell, Samsung |
| 20.1 | General | |
| R3-233742 | (BL CR to TS 37.483) Introduction of MT-SDT | Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Intel Corporation, China Telecom, Huawei, Lenovo, LG Electronics |
| R3-233744 | (BLCR to 38.401) Introduction on MT-SDT | Huawei, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Intel Corporation, China Telecom, Lenovo, LG Electronics |
| R3-233760 | (BLCR to 38.423) Introduction on MT-SDT | Ericsson, ZTE, Intel Corporation, Nokia, Nokia Shanghai Bell, China Telecom, Huawei, Lenovo |
| R3-233767 | (BLCR to 38.473) Introduction on MT-SDT | China Telecom, Intel Corporation, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-233778 | (BLCR to 37.480) Introduction on MT-SDT | LG Electronics, Nokia, Nokia Shanghai Bell |
| R3-233783 | (BLCR to 38.300) Introduction on MT-SDT | ZTE, CATT, Ericsson, China Mobile, China Telecom, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Google, LG Electronics |
| R3-233796 | (BLCR to 38.420) Introduction on MT-SDT | Lenovo, CATT, ZTE, Nokia, Nokia Shanghai Bell |
| R3-234805 | (BL CR to 37.483) Introduction of MT-SDT | Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Intel Corporation, China Telecom, Huawei, Lenovo, LG Electronics |
| R3-234806 | (BL CR to 38.300) Introduction on MT-SDT | ZTE, CATT, Ericsson, China Mobile, China Telecom, Nokia, Nokia Shanghai Bell, Lenovo, Huawei, Google, LG Electronics |
| R3-234807 | (BLCR to 38.401) Introduction on MT-SDT | Huawei, ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Intel Corporation, China Telecom, Lenovo, LG Electronics |
| R3-234833 | (BL CR to 37.480) Introduction on MT-SDT | Nokia, Nokia Shanghai Bell, Huawei, China Telecom, ZTE, LG Electronics, CATT, Ericsson |
| R3-234844 | (BLCR to 37.480) Introduction on MT-SDT | LG Electronics, Nokia, Nokia Shanghai Bell |
| 20.2 | Support for Paging-Triggered SDT | |
| R3-233819 | Discussion on MT-SDT | ZTE, Qualcomm Incorporated |
| R3-233820 | (TP to 37.483, 38.401) Leftove issues for MT-SDT | ZTE |
| R3-233832 | Remaining Issues on Supporting of MT-SDT | China Telecom |
| R3-233854 | Completion of MT-SDT Open Points | Nokia, Nokia Shanghai Bell, Orange |
| R3-233855 | (TP for TS 37.483) Completion of MT-SDT Open Points | Nokia, Nokia Shanghai Bell, Orange |
| R3-233976 | Signaling enhancements to enable MT-SDT for RRC_INACTIVE UEs. | Qualcomm Incorporated |
| R3-233977 | Draft LS on MT-SDT signalling optimization for partial context transfer. | Qualcomm Incorporated |
| R3-234087 | (TP to TS 37.480 BL CR) Consideration on remaining issues for MT-SDT | Huawei |
| R3-234088 | (TP to TS 38.401 BL CR) non-SDT or oversize SDT data arrival | Huawei, Qualcomm Incorporated |
| R3-234182 | Support for Paging-Triggered SDT | Lenovo |
| R3-234265 | Discussion on MT-SDT Open issues | Ericsson, Qualcomm Inc, ZTE, Lenovo |
| R3-234266 | (TP to TS 37.483 BL CR) MT-SDT Data Size configuration | Ericsson, Qualcomm Inc, ZTE, Lenovo |
| R3-234267 | (TP to TS 38.401 BL CR): Correction of MT-SDT DL Data Notification | Ericsson |
| R3-234268 | (TP to TS 38.300 BL CR): Miscellaneous fixes | Ericsson |
| R3-234351 | Discussions for open issues related to DL notification and data volume | LG Electronics Inc. |
| R3-234352 | Necessary corrections for stage-2 BL CRs (TPs for NR_MT_SDT BL CR for TS 38.300 and TS 38.401) | LG Electronics Inc. |
| R3-234362 | Discussion on leftover issues for MT-SDT | CATT |
| R3-234363 | (TP to BL CR for TS 38.401) Handling of non-SDT or oversized SDT data | CATT,China Telecom |
| R3-234489 | Remaining issues on MT-SDT | Samsung |
| R3-234534 | CB:R18SDT_Solution | ZTE |
| R3-234583 | (TP to TS 38.401 BL CR) Large SDT data arrival | Huawei, Qualcomm Incorporated,China Telecom, Nokia, Nokia Shanghai Bell, Samsung, Lenovo, LG Electronics, CATT, Ericsson |
| R3-234584 | (TP to 37.480) Introduction on MT-SDT | Nokia, Huawei, China Telecom, ZTE, LG Electronics, CATT, Ericsson |
| R3-234585 | (TP to TS 37.483 BL CR) Introduction of SDT Data Size threshold | Ericsson, Qualcomm Inc., ZTE, Lenovo, CATT, Nokia, Nokia Shanghai Bell,China Telecom, LG Electronics, Huawei |
| R3-234586 | (TP to 38.401) Leftover issues for MT-SDT | ZTE, China Telecom, CATT, Nokia, Nokia Shanghai Bell, Lenovo, LG Electronics, Ericsson, Google, Huawei |
| R3-234587 | (TP to 38.300) Leftover issues for MT-SDT | LG Electronics, ZTE, CATT, Nokia, Nokia Shanghai Bell, Ericsson, Google, Huawei |
| R3-234588 | (TP to 37.483) Leftover issues for MT-SDT | CATT |
| R3-234589 | LS on SDT signalling optimization for partial context transfer | RAN3(Qualcomm) |
| R3-234762 | (cancelled allocation) | Huawei |
| R3-234769 | (TP to TS 37.483 BL CR) Introduction of SDT Data Size threshold | Ericsson, Qualcomm Inc., ZTE, Lenovo, CATT, Nokia, Nokia Shanghai Bell,China Telecom, LG Electronics, Huawei, Samsung |
| R3-234770 | (TP to 37.483) Leftover issues for MT-SDT | CATT, China Telecom, ZTE, LGE, Nokia, Nokia Shanghai Bell |
| 21.1 | General | |
| R3-233753 | (BLCR to 38.413) Introduction of NR Redcap Enhancement | Huawei, Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-233786 | (BL CR to TS 38.300) Introduction of NR Redcap Enhancement | Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE |
| R3-233793 | (BLCR to 38.410) Introduction of NR Redcap Enhancement | CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-233800 | (BLCR to 38.423) Introduction of RedCap enhancement | Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-233808 | (BLCR to 38.473) Introduction on NR Redcap enhancement | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| R3-234271 | WI work plan for Rel-18 RedCap | Ericsson (Rapporteur) |
| R3-234812 | (BL CR to TS 38.300) Introduction of NR Redcap Enhancement | Nokia, Nokia Shanghai Bell, CATT, Ericsson, ZTE |
| R3-234813 | (BL CR to 38.410) Introduction of NR Redcap Enhancement | CATT, Nokia, Nokia Shanghai Bell, ZTE |
| R3-234814 | (BL CR to 38.413) Introduction of NR Redcap Enhancement | Huawei, Nokia, Nokia Shanghai Bell, ZTE, Ericsson |
| R3-234815 | (BL CR to 38.423) Introduction of RedCap enhancement | Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-234816 | (BLCR to 38.473) Introduction on NR Redcap Enhancement | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Huawei |
| 21.2 | Support Enhanced eDRX in RRC_INACTIVE | |
| R3-233726 | LS reply to RAN3 progress on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | SA2(Huawei) |
| R3-233821 | Discussion on NR Redcap enhancement | ZTE |
| R3-233822 | (TP to 38.413, 38.423, 38.473, 38.300) Introduction on NR Redcap | ZTE |
| R3-233856 | (TP for TS 38.413 and TS 38.410) Support of Extended eDRX for RRC Inactive over NG | Nokia, Nokia Shanghai Bell |
| R3-233857 | (TP for TS 38.470, TS 38.473 and TS 38.423) Support for R18 eRedcap | Nokia, Nokia Shanghai Bell |
| R3-233985 | Discussion on RRC Inactive with long eDRX for RedCap | Qualcomm Incorporated |
| R3-234115 | (TP for 38.413 and 38.410 for eRedCap) Discussion on MT Communication Handling | CATT |
| R3-234116 | (TP for eRedCap for 38.413, 38.423, 38.473) Discussion on Rel-18 long eDRX for RRC_INACTIVE | CATT |
| R3-234137 | (TP to TS 38.413 and 38.423) Further discussion on long eDRX support for RRC_INACTIVE UE | Huawei |
| R3-234138 | (TP to TS 38.473) Support of R18 eRedCap UE access | Huawei |
| R3-234139 | (TP to TS 38.423) Support of R18 eRedCap UE access | Huawei, China Unicom, China Telecommunication |
| R3-234140 | [Draft] Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | Huawei |
| R3-234272 | (TP to TS 38.413) Correction on DL Data Notification procedure name | Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, Qualcomm Inc., CATT |
| R3-234273 | (TPs to TSes 38.413/38.423/38.473 eRedCap BL CRs) Addition of long eDRX Paging Information for RRC_INACTIVE | Ericsson |
| R3-234274 | Discussion on eRedCap Indication with TPs and LS to SA2 | Ericsson |
| R3-234535 | CB:#R18Redcap | Ericsson |
| R3-234564 | (TP to TS 38.413) Correction on DL Data Notification procedure name | Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, Qualcomm Inc., CATT |
| R3-234565 | (TP for 38.410) Correction on DL Data Notification procedure name | CATT, Ericsson, Nokia, Nokia Shanghai Bell, ZTE, Huawei, CTC |
| R3-234566 | (TP for TS 38.413) Addressing issues in MT Communication Handling procedure | Nokia, Nokia Shanghai Bell, Ericsson, China Telecom |
| R3-234567 | (TP to 38.423) Introduction of RRC Inactive long eDRX | ZTE, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, China Telecom |
| R3-234568 | (TP to 38.473) Introduction of RRC Inactive long eDRX | Qualcomm Incorporated |
| R3-234569 | (TP to TS 38.423) Support of R18 eRedCap UE access | Huawei, China Unicom, China Telecommunication, Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R3-234570 | (TP to 38.473) Introduction of eRedCap broadcast information and NR eRedCap early Indication | CATT, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, Huawei |
| R3-234571 | Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | RAN3(Huawei) |
| R3-234572 | (TP for TS 38.300) Update of procedure name | Nokia, Nokia Shanghai Bell, Ericsson, Huawei |
| R3-234725 | Reply LS on Rel-18 RedCap enhancements to address remaining ENs in TS 23.502 | RAN3(Huawei) |
| R3-234729 | (TP to 38.473) Introduction of RRC Inactive long eDRX | Qualcomm Incorporated, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Huawei, China Telecom |
| 23.1 | General | |
| R3-233752 | Support of NR Positioning Enhancements | ZTE, CATT, Huawei, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-233761 | Support of NR Positioning Enhancements | Huawei, CATT, ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-233768 | Support of NR Positioning Enhancements | Ericsson, CATT, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-234590 | Summary of Positioning offline discussion | CATT |
| R3-234808 | Support of NR Positioning Enhancements | Ericsson, CATT, Huawei, ZTE, Nokia, Nokia Shanghai Bell |
| R3-234834 | Support of NR Positioning Enhancements | CATT |
| 23.2.1 | Sidelink Positioning | |
| R3-234032 | Discussion on sidelink positioning and others | Samsung |
| R3-234217 | Discussion on Carrier Phase Positioning and Sidelink Positioning | Huawei |
| R3-234254 | Discussion on sidelink positioning | Xiaomi |
| R3-234256 | (TP for BL CR to TS 38.455) Support of SRS bandwidth aggregation | Xiaomi, Samsung, ZTE |
| R3-234269 | Discussion on RAN3 impacts to support SL Positioning, CPP and other topics with TP for CPP support | Ericsson |
| R3-234327 | (TP for TS 38.455 BL CR) Positioning accuracy enhancements | Nokia, Nokia Shanghai Bell |
| R3-234364 | Discussion on SL Positioning BW aggregation and CPP | CATT |
| R3-234409 | (TP to 38.413, 38.423, 38.473,38.455) Discussion on Sidelink positioning | ZTE |
| R3-234451 | Discussion on NR SL Positioning | CMCC |
| R3-234496 | Discussion on Carrier Phase Positioning and Sidelink Positioning | Huawei |
| 23.2.2 | LPHAP | |
| R3-233714 | LS on LPHAP | RAN2(Huawei) |
| R3-234033 | Discussion on LPHAP | Samsung |
| R3-234218 | Discussion on LPHAP | Huawei |
| R3-234255 | Discussion on LPHAP positioning enhancement. | Xiaomi |
| R3-234270 | Discussion on RAN3 impacts to support LPHAP with TP | Ericsson |
| R3-234285 | Enhancements for LPHAP | Qualcomm Incorporated |
| R3-234326 | Coordination of SRS resources within a validity area | Nokia, Nokia Shanghai Bell |
| R3-234365 | (TP to BL CR for TS 38.305) Support of cross-cell SRS configuration | CATT |
| R3-234467 | (TP to 38.455, 38.473)Discussion on LPHAP impacts and SRS bandwith aggregation | ZTE |
| R3-234468 | Discussion on area-specific SRS configuration | vivo |
| 23.2.3 | Others | |
| R3-233706 | LS reply on the RAT-dependent positioning integrity | RAN1(Interdigital) |
| R3-233722 | LS on reporting granularity for timing related positioning measurements | RAN4(Huawei) |
| R3-234286 | Integrity of NR Positioning Technologies | Qualcomm Incorporated |
| R3-234596 | New TP for TS38.455 for NRPPa | Huawei, Samsung, CATT |
| R3-234597 | New TP for TS38.473 | Samsung, Huawei, CATT, Cybercore |
| R3-234602 | (TP for TS 38.455 BL CR) UL Carrier phase positioning | Nokia, Nokia Shanghai Bell, Ericsson, Huawei, CATT, ZTE |
| R3-234603 | (TP for TS 38.473 BL CR) UL Carrier phase positioning | Huawei, Nokia, Nokia Shanghai Bell, Ericsson, CATT, ZTE |
| R3-234604 | (TP to NRPPA BL CR) Addition or SRS Bandwidth Request indication | Ericsson, Xiaomi, ZTE, CATT, Samsung |
| R3-234605 | (TP for NR_pos_enh2 for TS 38.473) Support of SRS bandwidth aggregation | Xiaomi, Samsung, ZTE, Ericsson, CATT |
| R3-234726 | (TP BL CR 38.455) Reporting granularity for timing | Huawei, Samsung, CATT |
| R3-234727 | TP to BLCR 38.473 on reporting granularity for SRS BW aggregation | Samsung, Huawei, CATT, Cybercore |
| 24.1 | General | |
| R3-233798 | (BLCR to 38.423) Network energy saving techniques | Huawei, Samsung, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CATT, Intel |
| R3-233804 | (BLCR to 38.473) Introduction of Network Energy Saving | Ericsson, Huawei, Samsung, ZTE, CATT, Intel |
| R3-233990 | WI Work plan for R18 network energy savings | Huawei |
| R3-234783 | (BLCR to 38.423) Network energy saving techniques | Huawei, Samsung, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, CATT, Intel |
| R3-234784 | (BLCR to 38.473) Introduction of Network Energy Saving | Ericsson, Huawei, Samsung, ZTE, CATT, Intel |
| 24.2 | Support Network Energy Savings | |
| R3-233708 | Reply LS on Cell DTX/DRX activation/deactivation | RAN1(Huawei/Intel) |
| R3-233729 | Reply LS on the enhancements to restricting paging in a limited area | SA2(Qualcomm) |
| R3-233930 | Inter-node beam activation and paging enhancements | Qualcomm Incorporated |
| R3-233944 | Discussion on network energy saving | Samsung |
| R3-233945 | Introduction of Network Energy Saving for Paging IDLE UE | Samsung |
| R3-233991 | (TP to Netw_Energy_NR BLCR for TS 38.423) Network energy saving techniques | Huawei |
| R3-233992 | (TP to Netw_Energy_NR BLCR for TS 38.473, 38.413, 38.470 and 38.300) Network energy saving techniques | Huawei |
| R3-234134 | (TP to TS 38.423) Support of network energy saving techniques | Nokia, Nokia Shanghai Bell |
| R3-234135 | (TP to TS 38.473) Beam deactivation decision and signalling for energy saving | Nokia, Nokia Shanghai Bell |
| R3-234193 | Discussion on NES related issues | Lenovo |
| R3-234308 | Discussion on Cell DTX/DRX for NES | CATT |
| R3-234309 | (TPs to TS38.423/TS38.473 BL CR) Discussion on new cause and paging enhancement for NES | CATT |
| R3-234319 | Introduction of Network Energy Saving | Ericsson |
| R3-234320 | Text Proposal on F1AP: Introduction of Network Energy Saving | Ericsson |
| R3-234426 | left issues on network energy saving | ZTE |
| R3-234427 | TPs to BL CRs for network energy saving | ZTE |
| R3-234614 | CB:#R18ES | Huawei |
| R3-234668 | (TP to Netw_Energy_NR BLCR for TS 38.423) Network energy saving techniques | Huawei, Nokia, Nokia Shanghai Bell, ZTE, Ericsson, Qualcomm Incorporated, Samsung, CATT |
| R3-234669 | (TP to Netw_Energy_NR BLCR for TS 38.473) Introduction of Network Energy Saving | Ericsson |
| R3-234670 | (TP to Netw_Energy_NR BLCR for TS 38.300) Introduction of Network Energy Saving | ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-234771 | (TP to Netw_Energy_NR BLCR for TS 38.300) Introduction of Network Energy Saving | ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-234825 | (BL CR to 38.300) Introduction of Network Energy Saving | ZTE, Ericsson |
| 25.1 | General | |
| R3-234018 | Work Plan for Rel-18 on XR Enhancements for NR | Nokia, Qualcomm, Ericsson |
| R3-234836 | (BLCR to 37.483) Introducing enhancement for NR XR | Samsung, Ericsson, Nokia, Nokia Shanghai Bell, ZTE |
| R3-234837 | (BL CR to 38.300) for XR Enhancements | Qualcomm Inc, Ericsson, Nokia, Nokia Shanghai Bell, Huawei, ZTE |
| R3-234838 | (BL CR to 38.413) Support for NR XR | Nokia, Nokia Shanghai Bell, Ericsson, China Telecom, ZTE |
| R3-234839 | (XR BL CR to TS 38.415) Introduction of XR enhancements | ZTE, Ericsson, Nokia, Nokia Shanghai Bell, Qualcomm Inc |
| R3-234840 | Introduction of XR enhancement | Ericsson, ZTE |
| R3-234841 | (BL CR to 38.425) Support for NR XR | CMCC, Nokia, Nokia Shanghai Bell, Ericsson, ZTE, Qualcomm Inc |
| R3-234842 | (BL CR to 38.473) Support for NR XR | Huawei, Qualcomm Inc, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, ZTE |
| 25.2 | Support Enhancements on NR XR | |
| R3-233731 | LS reply on TSCAI for XR | SA2(VIVO) |
| R3-233732 | Reply LS on the N6 PDU Set Identification | SA2(OPPO) |
| R3-233733 | Reply LS on RAN information exposure for XRM | SA2(China mobile) |
| R3-233734 | LS Reply on Design of RTP Header Extension for PDU Set handling | SA2(Huawei) |
| R3-233735 | Non-homogeneous deployment of PDU Set based handling | SA2(Qualcomm) |
| R3-233950 | Discussion on the support of enhancement for NR XR | Samsung |
| R3-233951 | [TP for BLCR TS37.483] Introducing enhancement for NR XR | Samsung |
| R3-233952 | [TP for BLCR TS38.413, TS38.423] Introducing enhancement for NR XR mobility | Samsung |
| R3-233981 | TP for Stage-2 TS 38.300 for XR Enhancements | Qualcomm Incorporated |
| R3-234019 | Discussion on support for NR XR | Nokia, Nokia Shanghai Bell |
| R3-234020 | (TP for TS38.413) Support for NR XR | Nokia, Nokia Shanghai Bell |
| R3-234021 | Discussion on multiple LSs | Nokia, Nokia Shanghai Bell |
| R3-234119 | Discussion on Support Enhancements on NR XR | CATT |
| R3-234120 | Discussion on XR LSin from SA2 | CATT |
| R3-234121 | (TP for XR for 38.413, 37.483 and 38.473) Support Enhancements on XR awareness | CATT |
| R3-234153 | Discussion on discard operation for XR | Huawei, Qualcomm Inc. |
| R3-234154 | (TP for NR_XR_enh BL CRs) Discussion on the enhancement for XR awareness | Huawei, Qualcomm Inc. |
| R3-234155 | (TP for NR_XR_enh BL CR of TS 38.413) Discussion on incoming LS from other WGs | Huawei, Qualcomm Inc. |
| R3-234162 | Discussion on PDU Set QoS Parameters and PDU Set Information | Lenovo |
| R3-234163 | Discussion on PDU Set based Discard | Lenovo |
| R3-234164 | Discussion on ECN marking for L4S | Lenovo |
| R3-234257 | Discussion on enhancement for XR | Xiaomi |
| R3-234258 | (TPs for TS 38.300 and TS 38.413) Non-homogenous support of PDU set based handling | Xiaomi |
| R3-234275 | Discussion on XRM support | Ericsson |
| R3-234276 | Introduction of XRM enhancement | Ericsson |
| R3-234302 | Support for L4S in NG-RAN | Ericsson, Deutsche Telekom |
| R3-234406 | Disucssion on Support of XR Enhancement in Split Architecture | China Telecom |
| R3-234407 | BLCR to 38.401 on support of XR Enhancements | China Telecom |
| R3-234408 | (BLCR to 38.401) Introduction of XR enhancements | China Telecom |
| R3-234452 | Discussion on non-homogeneous deployment of PDU Set based handling | CMCC |
| R3-234482 | (TP to TS 38.413) Discussion on support of XR enhancements | ZTE |
| R3-234483 | (XR BL CR to TS 38.415) Introduction of XR enhancements | ZTE |
| R3-234484 | (TP to TS 38.423) Support of XR enhancements | ZTE |
| R3-234613 | CB:#R18XR | Nokia |
| R3-234651 | (TP for Stage-2 TS 38.300) for XR Enhancements | Qualcomm Inc, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-234652 | (TP for TS38.413) Support for NR XR | Nokia, Nokia Shanghai Bell, Ericsson, China Telecom |
| R3-234653 | (TP for NR_XR_enh BL CR for TS 38.473) Support for NR XR | Huawei, Qualcomm Inc, Ericsson, China Telecom, Nokia, Nokia Shanghai Bell, ZTE |
| R3-234654 | [TP for BLCR TS37.483] Introducing enhancement for NR XR | Samsung, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-234655 | (TP to TS 38.415) Discussion on support of XR enhancements | ZTE, Ericsson, Nokia, Nokia Shanghai Bell |
| R3-234656 | (TP to TS 38.423 BL CR) Addition of PDU Set QoS Parameters | Ericsson, ZTE |
| R3-234657 | (TP for TS38.425) Support for NR XR | CMCC, Nokia, Nokia Shanghai Bell, Ericsson, ZTE |
| R3-234772 | (TP to TS 38.415) Discussion on support of XR enhancements | ZTE, Ericsson, Nokia, Nokia Shanghai Bell |
| 26.1 | eNPN WI | |
| R3-233739 | (BLCR to 29.413) Support of the enhanced NPN phase 2 | Huawei, China Telecom, Nokia, Nokia Shanghai Bell, NEC, LG Electronics, ZTE, Samsung, Ericsson |
| R3-233746 | Support of the enhanced NPN phase 2 | ZTE, Nokia, Nokia Shanghai Bell, Huawei, NEC, LG Electronics, Samsung |
| R3-233779 | (BLCR to 38.300) On introduction of R18 eNPN | China Telecom, Huawei, ZTE, CATT, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, NEC, Ericsson |
| R3-233797 | Introduction of equivalent SNPNs | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, ZTE, NEC |
| R3-233830 | Introduction of equivalent SNPNs | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, ZTE, NEC |
| R3-233858 | Indicating selected SNPN over Xn for Further NPN Enhancements | Nokia, Nokia Shanghai Bell |
| R3-233859 | (TP for TS 38.423) Selected SNPN over Xn for further NPN Enhancements | Nokia, Nokia Shanghai Bell |
| R3-233873 | eNPN impact on RAN specifications | NEC |
| R3-233953 | Discussion on Enhanced support of NPN | Samsung |
| R3-233965 | (TP to eNPN_Ph2 BLCR for TS 38.413) Support of the enhanced NPN phase 2 | Huawei |
| R3-233966 | (TP to eNPN_Ph2 BLCR for TS 38.423) Support of the enhanced NPN phase 2 | Huawei |
| R3-234003 | Discussion on remaining issues to support eNPN | China Telecommunication |
| R3-234004 | (TP to BL CRs of 38.423) On support of eNPN | China Telecommunication |
| R3-234007 | Work Plan for Further Enhancement for Private Network Support for NG-RAN WI | China Telecommunication |
| R3-234117 | Discussion on RAN impact for NPN enhancement in Rel-18 | CATT |
| R3-234118 | [TP to 38.423 for eNPN] RAN impact for NPN enhancement in Rel-18 | CATT |
| R3-234235 | Remaining topics for Rel-18 eNPN work | Ericsson |
| R3-234236 | [TP for BL CR 38.413] Editorials for the NGAP BL CR | Ericsson |
| R3-234480 | left issues on RAN support for eNPN phase 2 | ZTE |
| R3-234481 | TPs to BL CRs for eNPN phase 2 | ZTE |
| R3-234487 | Remaining open issue in eNPN | LG Electronics |
| R3-234501 | Introduction of equivalent SNPNs | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, ZTE, NEC |
| R3-234533 | Support of the enhanced NPN phase 2 | ZTE, Nokia, Nokia Shanghai Bell, Huawei, NEC, LG Electronics, Samsung |
| R3-234551 | CB:#R18NPN_Solution | China Telecom |
| R3-234581 | (TP to eNPN_Ph2 BLCR for TS 38.423) Support of the enhanced NPN phase 2 | Huawei, Nokia, Nokia Shanghai Bell, China Telecom, CATT |
| R3-234582 | [TP for BL CR 38.413] Editorials for the NGAP BL CR | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, China Telecom, CATT, NEC |
| R3-234730 | (TP to eNPN_Ph2 BLCR for TS 38.423) Support of the enhanced NPN phase 2 | Huawei, Nokia, Nokia Shanghai Bell, China Telecom, CATT |
| R3-234776 | (BL CR to 38.413) Support of the enhanced NPN phase 2 | ZTE, Nokia, Nokia Shanghai Bell, Huawei, NEC, LG Electronics, Samsung |
| R3-234777 | Introduction of equivalent SNPNs | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, LG Electronics, Samsung, ZTE, NEC |
| 26.2 | Timing Resiliency and URLLC WI | |
| R3-233723 | Response to Reply LS on Proposed method for Time Synchronization status reporting to UE(s) | SA1(Nokia) |
| R3-233755 | (BLCR to 38.413) Introduction of 5G Timing Resiliency and URLLC enhancements | Huawei, China Unicom, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE, CATT |
| R3-233764 | (BL CR for TS 38.423) Introduction of 5G Timing Resiliency and URLLC enhancements | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung, ZTE, CATT |
| R3-233770 | (BLCR to 38.473) Introduction of 5G Timing Resiliency and URLLC enhancements | ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| R3-233814 | Work plan for Timing Resiliency and URLLC enhancements | Nokia (rapporteur) |
| R3-233815 | (TP for TS 38.401 BL CR) Stage 2 for timing resiliency and URLLC | Nokia, Nokia Shanghai Bell, Samsung, Qualcomm, CATT |
| R3-233816 | (TP for TS 38.413 BL CR) Further stage 3 details for timing resiliency | Nokia, Nokia Shanghai Bell |
| R3-233904 | Interworking with TSN network and RAN feedback | Nokia, Nokia Shanghai Bell |
| R3-233986 | Discussion on Open Issues in Timing Resiliency and uRLLC | Qualcomm Incorporated |
| R3-234023 | (TP to TRS_URLLC BLCR for TS 38.413, TS 38.423 and TS 38.473) Support of 5G Timing Resiliency enhancements | Huawei, China Unicom |
| R3-234024 | (TP to TRS_URLLC BLCR for TS 38.413, TS 38.423 and TS 38.473) Support of RAN feedback enhancements | Huawei, China Unicom |
| R3-234025 | (TP to TRS_URLLC BLCR for TS 38.413) Support of TSN enabled transport network | Huawei, China Unicom, China Telecommunication |
| R3-234321 | Discussion on NR Timing Resiliency and URLLC enhancements | Ericsson |
| R3-234322 | Text Proposals on Support NR Timing Resiliency and URLLC enhancements | Ericsson |
| R3-234396 | Discussion on Network timing synchronization status and reporting | CATT |
| R3-234397 | TP for BLCR to TS38.413 Adapting downstream and upstream scheduling | CATT |
| R3-234428 | Discussion and TPs for timing synchronization status and reporting | ZTE |
| R3-234429 | Discussion on TSN integration and RAN feedback | ZTE |
| R3-234552 | CB:#R18URLLC_Solution | Nokia |
| R3-234598 | (TP for TS 38.401 BL CR) TSS reporting | NokNokia, Nokia Shanghai Bell, Samsung, Qualcomm, CATT, Ericsson, Huawei, ZTE |
| R3-234599 | (TP for TS 38.413 BL CR) TSS reporting and RAN feedback | Huawei, China Unicom |
| R3-234600 | (TP for TS 38.473 BL CR) TSS reporting and RAN feedback | ZTE |
| R3-234601 | (TP for TS 38.423 BL CR) TSS reporting and RAN feedback | Ericsson |
| R3-234731 | (TP for TS 38.473 BL CR) TSS reporting and RAN feedback | ZTE, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-234821 | (BLCR to 38.413) Introduction of 5G Timing Resiliency and URLLC enhancements | Huawei, China Unicom, Nokia, Nokia Shanghai Bell, Samsung, Ericsson, ZTE, CATT |
| R3-234822 | (BL CR to 38.423) Introduction of 5G Timing Resiliency and URLLC enhancements | Ericsson, Huawei, Nokia, Nokia Shanghai Bell, Samsung, ZTE, CATT |
| R3-234823 | (BL CR to 38.473) Introduction of 5G Timing Resiliency and URLLC enhancements | ZTE, Huawei, Ericsson, Nokia, Nokia Shanghai Bell, Samsung |
| R3-234843 | (BL CR for TS 38.401) Introduction of 5G Timing Resiliency and URLLC enhancements | Nokia, Nokia Shanghai Bell, Samsung, Qualcomm, CATT, Ericsson, Huawei, ZTE |
| 26.3 | RAN Slicing WI | |
| R3-233747 | Introduction of Enhancement of RAN Slicing for NR | Nokia, Nokia Shanghai Bell |
| R3-233860 | (TP for TS 38.413 and TS 38.423) Support of Network Slice Service Continuity | Nokia, Nokia Shanghai Bell, Orange |
| R3-233861 | (TP for TS 38.413 and TS 38.423) Support of partially allowed S-NSSAI in RRC connected mode | Nokia, Nokia Shanghai Bell, Orange |
| R3-233962 | (TP to eNS_Ph3 BLCR for TS 38.300) Enhanced network slicing phase 3 | Huawei |
| R3-233963 | (TP to eNS_Ph3 BLCR for TS 38.413) Partially allowed NSSAI in a registration area | Huawei |
| R3-234005 | Discussion on remaining issues for RAN Slicing enhancement | China Telecommunication |
| R3-234006 | (TP to TS 38.300/38.413) Support of Partially Allowed S-NSSAI | China Telecommunication |
| R3-234034 | Further discussion on the enhancement of RAN slicing | Samsung |
| R3-234303 | Clarifications on Partially Allowed NSSAI | Ericsson, Deutsche Telekom |
| R3-234304 | Clarifications and Way Forward on Network Slice Service Continuity | Ericsson |
| R3-234398 | Discussion on supporting Partially Allowed NSSAI | CATT |
| R3-234399 | TP for 38.423 for supporting alternative S-NSSAI | CATT |
| R3-234419 | (TPs for BLCRs for 38.413 38.423 38.473 38.300)RAN impact on supporting Network Slice Service continuity scenario | ZTE |
| R3-234420 | (TPs for BLCRs for TS 38.413)RAN impact on support Partially Allowed NSSAI | ZTE |
| R3-234448 | Discussion on network slice service continuity | CMCC |
| R3-234449 | Discussion on Partially Allowed NSSAI | CMCC |
| R3-234507 | Clarifications on Partially Allowed NSSAI | Ericsson, Deutsche Telekom, Bell Mobility |
| R3-234553 | CB:#R18Slice_Solution | ZTE |
| R3-234676 | TP for BLCRs for TS 38.413 Enhancement of RAN Slicing for NR | ZTE, Nokia,Nokia Shanghai Bell, Ericsson,Huawei,China Telecom,China Mobile |
| R3-234691 | (TP for BLCRs for TS 38.300) Enhancement of RAN Slicing for NR | China Telecom, Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| R3-234778 | (BL CR to 38.413) Introduction of Enhancement of RAN Slicing for NR | Nokia, Nokia Shanghai Bell |
| R3-234824 | (BL CR to 38.300) Enhancement of RAN Slicing for NR | ZTE, China Telecom, Nokia, Nokia Shanghai Bell, Huawei, Ericsson |
| 31.1 | Corrections | |
| R3-233946 | Discussion on HARQ Related Assistance Information in NR User Plane | Samsung, China Telecom, CMCC, Lenovo |
| R3-233947 | Correction for HARQ Related Assisstance Information in NR User Plane | Samsung, China Telecom, CMCC, Lenovo |
| R3-233964 | Introduction of measurements without gap with interruption | Huawei, Deutsche Telekom, BT |
| R3-234213 | TEI18 RedCap UE MBS broadcast reception | ZTE |
| R3-234337 | Correction of MBS Multicast HFN/SN Initialization | Nokia, Nokia Shanghai Bell, CATT, Orange, Qualcomm Incorporated |
| R3-234485 | Discussion on corrections of PDU session split | ZTE, CMCC, China Telecom, China Unicom |
| R3-234486 | Corrections of PDU session split | ZTE, CMCC, China Telecom, China Unicom |
| R3-234536 | CB:#11_PDUSesseionSplit | ZTE |
| R3-234537 | CB 12_MBSBroadcat | ZTE |
| R3-234710 | Corrections of PDU session split | ZTE, CMCC, China Telecom, China Unicom |
| R3-234715 | LS on RedCap UE MBS Broadcast reception | ZTE |
| R3-234735 | LS on RedCap UE MBS Broadcast reception | RAN3(ZTE) |
| 31.2 | Enhancements | |
| R3-233823 | Dicusison on SDT termination for split gNB | ZTE |
| R3-233831 | Timing Advance Exceeded Cause | Nokia, Nokia Shanghai Bell |
| R3-233841 | Location Reporting Correction | Ericsson, China Telecom, Huawei, CATT, China Unicom |
| R3-233863 | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | ZTE, Nokia, Nokia Shanghai Bell, Huawei |
| R3-234091 | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE |
| R3-234104 | LMF Outage Reporting [LMF_outage] | Ericsson |
| R3-234220 | Discussion on positioning in inactive mode for SDT without anchor relocation | Huawei, CATT |
| R3-234221 | Positioning inactive mode for SDT without anchor relocation | Huawei, CATT |
| R3-234229 | TEI18 RRC Inactive enhancements | Ericsson |
| R3-234237 | On MRB PDCP COUNT wrap around including [draft CRs for several TSs] | Ericsson |
| R3-234238 | Timing Advance Exceeded Cause [TA-Cause] | Nokia, Nokia Shanghai Bell |
| R3-234239 | Timing Advance Exceeded Cause [TA-Cause] | Nokia, Nokia Shanghai Bell |
| R3-234277 | Information on posSIBs relaying to remote UE [PosL2RemoteUE] | Ericsson, AT&T, Deutsche Telekom |
| R3-234338 | Switching from SDT to RRC Connected State [Large SDT Uplink Data] | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, ZTE |
| R3-234339 | Relocation of MBS Contexts to another CU UP | Nokia, Nokia Shanghai Bell |
| R3-234366 | Discussion on Inactive Positioning in SDT without anchor relocation | CATT, Huawei |
| R3-234367 | Support of Inactive Positioning in SDT without UE context relocation case | CATT, Huawei |
| R3-234430 | Correction on Location reporting control | ZTE, Huawei, CATT, China Telecom, China Unicom, Qualcomm |
| R3-234488 | Information on posSIBs relaying to remote UE [PosL2RemoteUE] | Ericsson, AT&T, Deutsche Telekom |
| R3-234555 | CB: # 26_ULdataSDT | ZTE |
| R3-234556 | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | ZTE, Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, CATT, LG Electronics, China Telecom, Samsung, Ericsson |
| R3-234557 | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE |
| R3-234558 | Switching from SDT to RRC Connected State [Large SDT Uplink Data] | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, ZTE |
| R3-234561 | Location Reporting Enhancement | Ericsson, China Telecom, Huawei, CATT, China Unicom |
| R3-234562 | Correction on Location reporting control | ZTE, Huawei, CATT, China Telecom, China Unicom, Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson |
| R3-234616 | Timing Advance Exceeded Cause [TA-Cause] | Nokia, Nokia Shanghai Bell, Reliance Jio |
| R3-234685 | Location Reporting Enhancement | Ericsson, China Telecom, Huawei, CATT, China Unicom |
| R3-234736 | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | ZTE, Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, CATT, LG Electronics, China Telecom, Samsung, Ericsson |
| R3-234737 | Support of oversize UL SDT Data Arrival [Large SDT Uplink Data] | Huawei, Nokia, Nokia Shanghai Bell, Qualcomm Incorporated, ZTE, LG Electronics,China Telecom, Samsung, Ericsson |
| R3-234738 | Switching from SDT to RRC Connected State [Large SDT Uplink Data] | Nokia, Nokia Shanghai Bell, Huawei, Qualcomm Incorporated, ZTE |
| R3-234774 | Correction on Location reporting control [LRC-Enh] | ZTE, Huawei, CATT, China Telecom, China Unicom, Qualcomm, Nokia, Nokia Shanghai Bell, Ericsson |